Uploaded image for project: 'Flume'
  1. Flume
  2. FLUME-2394

Command line argument to disable monitoring for config changes

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: 1.5.0
    • Fix Version/s: 1.6.0
    • Component/s: Configuration
    • Labels:
      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

        Attachments

          Activity

            People

            • Assignee:
              paliwalashish Ashish Paliwal
              Reporter:
              rahulrv Rahul Ravindran
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: