[
https://issues.apache.org/jira/browse/FLUME-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880850#comment-15880850
]
bharat commented on FLUME-849:
------------------------------
I was playing around with this one, when the user remove source1 and add source
2 both of them are not started and source 1 is actually stopped. The way new
configuration changes are applied is that:
1. stop all components on the existing configuration
2. now set the new configuration
3. start all components (this will work on new configuration)
source/sink/channel have stop time != 0 in case it was removed.
Although I am not sure if a source/sink/channel is added again then existing
channel is restarted or a new one is created.
> Configuration changes can not remove already configured components
> ------------------------------------------------------------------
>
> Key: FLUME-849
> URL: https://issues.apache.org/jira/browse/FLUME-849
> Project: Flume
> Issue Type: Bug
> Components: Configuration
> Affects Versions: NG alpha 1
> Reporter: E. Sammer
>
> When Flume receives a configuration change event (via
> onConfigurationChange()) it can not detect the removal of configuration.
> For instance, if source 1 is configured and the user removes source 1 and
> adds source 2 Flume will now have both started rather than just source 2.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
