[
https://issues.apache.org/jira/browse/FLUME-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488498#comment-13488498
]
Denny Ye commented on FLUME-1665:
---------------------------------
Primary purpose of my method is waiting the Sink thread exit but not interrupt.
I think it's fit for notion of transaction than original process. Old code at
SinkRuner may break out transaction even if events has being consumed normally
and rollback whole transaction, then retry whole transaction to new file.
Events of that transaction before rollback have duplicated.
hi Hari, would you show me an example that any thing cannot make sense from my
modification(remove 'interrupt' action, 100th lines at SinkRunner.java)?
> 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
