Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
1.5.0
-
None
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