[
https://issues.apache.org/jira/browse/FLUME-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210217#comment-15210217
]
Ryan Persaud commented on FLUME-2885:
-------------------------------------
Ambud, datagramSize is an optional configuration. If the user specifies it in
flume.conf, then that value is used. If the user does not specify it in, then
the default of 2K is used.
> 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)
