[
https://issues.apache.org/jira/browse/FLUME-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559345#comment-13559345
]
Juhani Connolly commented on FLUME-1860:
----------------------------------------
Hmm, I suspect with some careful coding you could replace the transaction
buffer with an array. The preconditions in MemoryChannel are pretty strict to
make sure rollback is always possible, you'll need to watch out for that if you
choose to switch to using an array.
As to giving a hint of the batch size... I suppose it could be done but it
would add stronger coupling between components as they would need a heightened
awareness of one another.
> 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
