[
https://issues.apache.org/jira/browse/FLUME-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557515#comment-13557515
]
Hari Shreedharan commented on FLUME-1860:
-----------------------------------------
But doing something like this would create a tight coupling between config
params (it already does, the sink's batch size has to be <= the next hop's
transaction capacity). I don't really know if there is a way to resolve this
issue without such a tight coupling, but it would be nice if there was.
> 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
