You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2014/07/02 00:57:24 UTC

[jira] [Commented] (FLUME-2404) Default maxReadBufferBytes might cause OOM and cause scribe source exit

    [ https://issues.apache.org/jira/browse/FLUME-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049412#comment-14049412 ] 

Mike Percy commented on FLUME-2404:
-----------------------------------

[~chenshangan521@163.com], can you please take a look at FLUME-2405 as well? Seems to be related, and although I am not very familiar with how Scribe works, it seems we should use compatible defaults for both.

Thanks,
Mike

> 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
>         Attachments: 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)