You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flume.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2013/01/18 20:58:13 UTC

[jira] [Comment Edited] (FLUME-1860) Remove transaction capacity from Memory and File channels

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

Brock Noland edited comment on FLUME-1860 at 1/18/13 7:56 PM:
--------------------------------------------------------------

I like bumping it to 10K so it almost never gets in the way of normal use. It serves it's purpose as a sanity check and otherwise doesn't bother the humans.
                
      was (Author: brocknoland):
    I like bumping it to 10K so it almost never gets in the way of normal use. It sures it's purpose as a sanity check and otherwise doesn't bother the humans.
                  
> Remove transaction capacity from Memory and File channels
> ---------------------------------------------------------
>
>                 Key: FLUME-1860
>                 URL: https://issues.apache.org/jira/browse/FLUME-1860
>             Project: Flume
>          Issue Type: Bug
>            Reporter: Hari Shreedharan
>
> Transaction Capacity was primarily meant to be a memory safeguard. It ensures that we don't have queues which are massive and can cause OOMs. I wonder if there is a way of fixing this and making sure a malicious RpcClient cannot cause OOMs by sending batches of huge sizes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira