Reduce UDP RcvbufErrors under high traffic bursts
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go, linux
- Domain
- networking, performance
Research direction
The payload names no source files. Start by finding where the collector opens its UDP listening socket and check whether it sets a receive buffer size. Reproduce drops by watching the RcvbufErrors counter in /proc/net/snmp under a burst. The issue asks for an opinion before any change, so a first contribution would be a proposal: make SO_RCVBUF configurable, then discuss goroutine reads and recvmmsg separately. Done means the buffer size is settable and the drop counter can be verified.
Written by the indexing model from the issue text.
Description
Under high traffic bursts, I consistently see the kernel UDP receive buffer error counter (RcvbufErrors) increase, indicating that datagrams are dropped even before they reach goflow2.
Make SO_RCVBUF configurable, so we can increase it if necessary.
I also thought about reading from the socket. Can it be done with more than 1 goroutine ? That could also help this problem. Another idea is to use batched reads via recvmmsg.
This problem only appeared in extremely high bursts of IPFIX data and all drops happened on the socket as goflow2 metrics for drops were 0. I would like your opinion on if these ideas could be helpful.
- Dominant language
- Go
- Stars
- 817
- Forks
- 182
- Avg merge
- 4h 18m
- Merged PRs (30d)
- 6
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from netsampler/goflow2
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
netsampler/goflow2#601 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
netsampler/goflow2#539 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
netsampler/goflow2#528 ·
Maintainers usually reply within 1 day
-
NetFlow v9: zero OUT_BYTES/OUT_PKTS (FreeBSD ng_netflow/OPNsense) overwrite real IN_BYTES/IN_PKTS — bytes always 0Possibly taken @devMaxMcCann claimed this 8 days ago. Open
Difficulty 3/5 Half a day Newbie friendliness 52/100
netsampler/goflow2#524 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 28/100
netsampler/goflow2#522 ·
Maintainers usually reply within 1 day
All issues in netsampler/goflow2
Similar issues
-
enhancement exporter/awskinesis needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/opentelemetry-collector-contrib#53334 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
erigontech/erigon#26523 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
SocialGouv/iterion#3376 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
seaweedfs/seaweedfs#12740 · 2 comments ·
Maintainers usually reply within 1 day
-
area:indexer bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#385 ·
Maintainers usually reply within 1 day