influxdata / influxdata/kapacitor
Sudden increase `TCP_alloc` and `filefd`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
I use `# lsof -n |awk '{print $2}'|sort|uniq -c |sort -nr` lookup the file descriptor ,
kapacitor is the top of one
find problematic task
```
dbrp "course_support"."autogen"
var watchData = stream
| from()
.database('course_support')
.retentionPolicy('autogen')
.measurement('WATCH')
| httpPost('http://172.21.243.98/api/kapacitor/write').header('db','course_support').header('measurement','WATCH')
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported lsof/awk command and the Kapacitor task containing the stream, database, measurement, and httpPost configuration. Investigate the reported TCP_alloc and filefd increase, then establish a reproducible cause and a testable fix; the issue does not specify a target file or expected completed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- awk, shell
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100