[
https://issues.apache.org/jira/browse/FLUME-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052746#comment-14052746
]
Hudson commented on FLUME-2404:
-------------------------------
SUCCESS: Integrated in Flume-trunk-hbase-98 #4 (See
[https://builds.apache.org/job/Flume-trunk-hbase-98/4/])
FLUME-2404. Make ScribeSource read buffer and max frame size configurable
(mpercy:
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=f15f20785262ac3cb3e35c2a12e669b7a836d35f)
*
flume-ng-sources/flume-scribe-source/src/main/java/org/apache/flume/source/scribe/ScribeSource.java
* flume-ng-doc/sphinx/FlumeUserGuide.rst
> Default maxReadBufferBytes might cause OOM and cause scribe source exit
> -----------------------------------------------------------------------
>
> Key: FLUME-2404
> URL: https://issues.apache.org/jira/browse/FLUME-2404
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.5.0
> Reporter: chenshangan
> Assignee: chenshangan
> Fix For: v1.6.0
>
> Attachments: FLUME-2404-2.patch, FLUME-2404.patch
>
>
> We're using scribe source, some hacker like infosec guys send some malicious
> frames to flume with the frame size field set to a very big integer, then the
> thrift server inside scribe source will exit due to OOM. Then scribe source
> will keep wait_close state and can not accept any connection.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
