Add receive_buffer_bytes option and read full-size UDP datagrams - #81
Open
peninoule wants to merge 1 commit into
Open
Add receive_buffer_bytes option and read full-size UDP datagrams#81peninoule wants to merge 1 commit into
peninoule wants to merge 1 commit into
Conversation
|
💚 CLA has been signed |
peninoule
marked this pull request as ready for review
August 17, 2026 16:32
The UDP listener never calls setsockopt, so the socket receive buffer is stuck at the OS default (net.core.rmem_default, ~208KiB on Linux). Under a log burst the buffer fills in milliseconds and the kernel silently drops datagrams (visible as Udp RcvbufErrors). Add the receive_buffer_bytes option, mirroring logstash-input-udp, so users can request a larger buffer up to net.core.rmem_max. Also read up to 65536 bytes per datagram instead of 8192, so unchunked GELF datagrams larger than 8KiB are no longer truncated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
peninoule
force-pushed
the
receive-buffer-bytes
branch
from
August 18, 2026 07:46
838b798 to
11fb768
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The UDP listener never calls setsockopt, so the socket receive buffer is stuck at the OS default (net.core.rmem_default, ~208KiB on Linux).
Under a log burst the buffer fills in milliseconds and the kernel silently drops datagrams (visible as Udp RcvbufErrors).
Add the receive_buffer_bytes option, mirroring logstash-input-udp, so users can request a larger buffer up to net.core.rmem_max.
Also read up to 65536 bytes per datagram instead of 8192, so unchunked GELF datagrams larger than 8KiB are no longer truncated.