[
https://issues.apache.org/jira/browse/FLUME-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196245#comment-15196245
]
ASF GitHub Bot commented on FLUME-2885:
---------------------------------------
GitHub user ryanpersaud opened a pull request:
https://github.com/apache/flume/pull/45
Fixes to address 2K message size limit when using SyslogUDPSource.
Please see https://issues.apache.org/jira/browse/FLUME-2885. Currently,
the SyslogUDPSource is limited to messages <= 2K. With this fix, the default
behavior remains the same (2K is used for the buffer size), but if a user
specifies a value for datagramSize in the flume configuration, then that size
is used instead. If we want to use AdaptiveReceiveBufferSizePredictor to avoid
allocating buffers that are too large, 'someone' is going to have to develop a
more comprehensive fix. This at least allows for udp syslog users with
messages larger than 2K to process their messages without truncation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ryanpersaud/flume trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flume/pull/45.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #45
----
commit 8efafda2ac7798f3df26d4de309fa9d9d6c81348
Author: Ryan Persaud <[email protected]>
Date: 2016-03-15T20:37:49Z
Fixes to address 2K message size limit when using SyslogUDPSource.
----
> Handle payloads larger than 2k via SyslogUDPSource
> --------------------------------------------------
>
> Key: FLUME-2885
> URL: https://issues.apache.org/jira/browse/FLUME-2885
> Project: Flume
> Issue Type: Bug
> Reporter: Javier León de Antonio
>
> Syslog messages sent via UDP are truncated to 2k.
> After a research, I found this issue :
> https://issues.apache.org/jira/browse/FLUME-2130
> I saw you are using an AdaptiveReceiveBufferSizePredictorFactory to handle
> the buffer size from an initial size of 2k to a max size of 64k, but this
> BufferSizePredictor never grows. I searched a little more, and I found that
> AdaptiveReceiveBufferSizePredictorFactory only does his magic on
> NioDatagramWorker.
> SyslogUDPSource is not using NIO to handle UDP (It's using
> OioDatagramChannelFactory), so NioDatagramWorker is not been used.
> I don't know if it's better to change netty server to work with NIO on
> SyslogUDPSource, or to put 64k as buffer initial value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
