You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Rahul Ravindran (JIRA)" <ji...@apache.org> on 2014/06/04 07:33:01 UTC
[jira] [Created] (FLUME-2394) Command line argument to disable
monitoring for config changes
Rahul Ravindran created FLUME-2394:
--------------------------------------
Summary: 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 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)