[
https://issues.apache.org/jira/browse/FLUME-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488467#comment-13488467
]
Denny Ye commented on FLUME-1665:
---------------------------------
hi Mike, actually there have final acknowledgement of transaction. Either
success or failed of transaction, it must to check the thread status
'shouldStop'. In my opinion, what we should do is still ensuring the whole
transaction and don't interrupt it. Just let whole transaction go, don't care
about any exceptions. After that transaction, Sink thread will exit by
'shouldStop=true' status set by configuration checker thread (99th lines at
SinkRunner).
OK, this method may spend time to wait the end of Sink thread, but it's worth
for keeping integrated transaction.
> 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
