Flume
  1. Flume
  2. FLUME-2394

Command line argument to disable monitoring for config changes

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Not a Problem
    • Affects Version/s: v1.5.0
    • Fix Version/s: v1.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

        Activity

        Hide
        Ashish Paliwal added a comment -

        Use no-reload-conf option. This ignores the configuration file changes. Documentation needs to be updated for this.
        IMHO, better to ask question on User ML.

        Show
        Ashish Paliwal added a comment - Use no-reload-conf option. This ignores the configuration file changes. Documentation needs to be updated for this. IMHO, better to ask question on User ML.
        Hide
        Ashish Paliwal added a comment -

        no-reload-config option exist for the same purpose

        Show
        Ashish Paliwal added a comment - no-reload-config option exist for the same purpose

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development