[
https://issues.apache.org/jira/browse/FLUME-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488500#comment-13488500
]
Mike Percy commented on FLUME-1665:
-----------------------------------
This sounds like an argument for a more-graceful shutdown procedure. Adding
more gracefulness to the shutdown procedure wouldn't necessarily be bad, but on
the other hand we can't wait forever, since most stop scripts I have seen (in
Bigtop and elsewhere) have a built-in kill -9 after 30 seconds or so, which we
would do well to avoid. Hari is right that we need to be very careful about the
consequences of a delayed shutdown of any one component on the rest of the
system. I feel that a design proposal for comprehensive improvements to the
agent reconfig/shutdown process would need to be discussed in order to properly
approach this.
> 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
