[
https://issues.apache.org/jira/browse/FLUME-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488495#comment-13488495
]
Hari Shreedharan commented on FLUME-1665:
-----------------------------------------
Denny - This change would require that the semantics of Flume should change.
You can make such changes only in major releases and not minor. Again, the
notion of transaction is that one failure will cause the entire batch to be
retried. That is how it is supposed to be. Unless a transaction is completed,
the channel has no way of knowing if the transaction completed or not.
We *must* consider a transaction as one unit, so one failure is the failure of
the entire transaction - there is no way around it.
> Data from FileChannel will be duplicated when restarting configuration
> ----------------------------------------------------------------------
>
> Key: FLUME-1665
> URL: https://issues.apache.org/jira/browse/FLUME-1665
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Affects Versions: v1.2.0, v1.3.0
> Reporter: Denny Ye
> Labels: FileChannel
>
> When Flume process was running, I changed configuration property and Flume
> rebooted without process restarting. Events will be duplicated in next loop,
> also has been consumed before all components have stopped.
> I found the root cause. When FileChannel was stopping, it should save the
> 'inflightPuts' and 'inflightTakes' into disk for preparing in next loop.
--
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
