[
https://issues.apache.org/jira/browse/FLUME-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Ravindran updated FLUME-2394:
-----------------------------------
Description: Flume monitors for changes to the config file and attempts to
re-initialize source/sinks/channels based on detected changes. However, this
does not work for all config values, and also in undesirable in a lot of
production environments where puppet/chef modifies the config, and likely
restarts flume. It would be good to have an optional command line argument
which would disable this monitoring and require flume to be restarted for
config changes. We can control the restart using variety of orchestration
mechanisms (was: Flume monitors for changes to the config file and attempts to
re-initialize source/sinks/channels based on detected changes. However, this
does not work for all config values, and also in undesirable in a lot of
production environments where puppet/chef modifies the config, and likely
restart flume. It would be good to have an optional command line argument which
would disable this monitoring and require flume to be restarted for config
changes.)
> Command line argument to disable monitoring for config changes
> --------------------------------------------------------------
>
> Key: FLUME-2394
> URL: https://issues.apache.org/jira/browse/FLUME-2394
> Project: Flume
> Issue Type: New Feature
> Components: Configuration
> Affects Versions: v1.5.0
> Reporter: Rahul Ravindran
> Fix For: v1.6.0
>
>
> Flume monitors for changes to the config file and attempts to re-initialize
> source/sinks/channels based on detected changes. However, this does not work
> for all config values, and also in undesirable in a lot of production
> environments where puppet/chef modifies the config, and likely restarts
> flume. It would be good to have an optional command line argument which would
> disable this monitoring and require flume to be restarted for config changes.
> We can control the restart using variety of orchestration mechanisms
--
This message was sent by Atlassian JIRA
(v6.2#6252)
