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

Sysinit startup not possible

    XMLWordPrintableJSON

Details

    Description

      Atm flume isn't ready to start via sysinit, because its need a agent definition at startup:
      bin/flume-ng agent -n NAME -f conf/flume-conf.properties.template

      which reflect the name.foo in the config files. An easy improvement could be to improve the Node name check from missing node name into all node names.

      Tech:
      ====
      bin/flume-ng agent -f conf/flume-conf.properties.template
      java.lang.IllegalStateException: Node name not specified in node.Application (Application.java):

      Code:
      Preconditions.checkState(configurationFile != null,
      "Configuration file not specified");
      Preconditions.checkState(nodeName != null, "Node name not specified");

      Here flume nodeManager could iterate over all name.foo and start all flows. If one or more fails, throw an exception and go to the next available.

      Attachments

        Activity

          People

            alo.alt Alexander Alten-Lorenz
            alo.alt Alexander Alten-Lorenz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: