[
https://issues.apache.org/jira/browse/FLUME-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559280#comment-13559280
]
Juhani Connolly commented on FLUME-1860:
----------------------------------------
Roshan: The transaction size is only used as a limit to how large the queue can
get, it doesn't allocate that memory in advance. The only thing giving the
batch size would help with would be allowing us to fail early where batch sizes
are > transaction size.
Hari: I think the larger issue with RPC clients is the sources/protocols
themselves. The thrift in scribesource will OOM you if you send it a bad packet
without anything ever reaching the channel. AvroSource is somewhat better
behaved in that a huge batch is detected and flagged as an error without an
attempt to allocate.
> 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
