[
https://issues.apache.org/jira/browse/FLUME-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558983#comment-13558983
]
Roshan Naik commented on FLUME-1860:
------------------------------------
Currently the transaction capacity is used by the (memory) channel to size the
put/take lists. It is usually unnecessary to size them any larger than the
batchsize of the source or sink that is instantiating the transaction.
It would be useful for the transaction to be given a batch size hint at the
time of createTransaction().
Right now we dont have this ability to pass such a hint to the transaction. I
think it would be worthwhile tackling this issue as well along with this.
> 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
