[
https://issues.apache.org/jira/browse/FLUME-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289180#comment-13289180
]
Juhani Connolly commented on FLUME-1255:
----------------------------------------
I agree that the current failing with an exception isn't ideal, but I think
this is a limitation of the Channel interface, not necessarily one of the
individual component implementations. We can only communicate one of three
things:
- "Here's some data we got for you"
- "Sorry no more data"
- "Something's wrong"
The last "something's wrong" is probably too vague. When the transaction is
full, saying "no more data" is plain wrong.
The only "correct" solution I can see is adding a mechanism to allow more
specific communication between the components, in this case
TransactionLimitException or something that tells a source/sink that everything
is ok, but they can't handle more until the current transaction is committed.
Do you(or anyone else) have any other ideas how to get around this?
> Channels should not throw exceptions in channel.take if it has reached txn
> capacity
> -----------------------------------------------------------------------------------
>
> Key: FLUME-1255
> URL: https://issues.apache.org/jira/browse/FLUME-1255
> Project: Flume
> Issue Type: Bug
> Reporter: Hari Shreedharan
>
> Channels like Memory channel throw exception when reaching txn capacity. If
> sink's batchsize is more than txn capacity the take function throws exception.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
