You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Hari Shreedharan (JIRA)" <ji...@apache.org> on 2013/01/18 20:04:17 UTC
[jira] [Updated] (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:all-tabpanel ]
Hari Shreedharan updated FLUME-1860:
------------------------------------
Description: 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
> 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