[
https://issues.apache.org/jira/browse/FLUME-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253659#comment-13253659
]
Hari Shreedharan commented on FLUME-1121:
-----------------------------------------
I agree with the general changes, but I have a concern here. If the channel
capacity is N, then only a total of N events should ever be there in the
channel, regardless of failure. What I am saying is this:
A) K events are committed to disk, and the agent fails. (K < N)
B) J events are attempted to be written to the channel(assuming no sink or slow
sink, which has not yet cleared any of the K events). If K+J > N, then only a
total of N events should be written to the channel, and the rest(K+J-N) should
return failure. Eg: K= 99, J= 5, then after the first of the 2nd lot of 5
events are written, the channel * should * fail.
Else, the capacity of the channel is simply an implementation detail, and does
not hold any real value. It is really the capacity of the memory channel held
internally.
Ideally, the moment there are more than N events in the channel (fail or not),
the channel returns failure to append more events. As far as a client calling
this is concerned, it does not matter how it is implemented internally, the
channel should not have more than N events.
> Recoverable Memory Channel cannot recover data
> -----------------------------------------------
>
> Key: FLUME-1121
> URL: https://issues.apache.org/jira/browse/FLUME-1121
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.2.0
> Reporter: Hari Shreedharan
>
> Run an agent with a source, like seq with a recoverable memory channel and no
> sink. kill the process with ctrl-C. Run an agent now with no source, but
> logger sink and the same recoverable memory channel. I expected the events
> generated by the source earlier should be written to the sink, but no events
> with picked up.
--
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
