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

flume-ng --conf parameter is not used when starting a flume agent

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: 1.4.0
    • Fix Version/s: 1.7.0
    • Component/s: Node
    • Labels:
    • Environment:

      ubuntu 12 & Flume 1.4.0

      Description

      flume-ng script accepts the parameter conf to pass the directory which stores the configuration files and adds it to the FLUME_CLASSPATH. But org.apache.flume.node.Application expects configuration files passed to have an absolute path. So even if user passes `conf` and `conf-file` option, `application` looks for the configuration file in the directory from which it is executed. It would be good to take the `conf` value into consideration so that users can place the config files anywhere.

      Currently big-top init.d script joins the `conf` and `conf-file` values when calling flume-ng. The same can be done in the ` flume-ng ` script. Alternatively the `conf ` parameter can be read in ` application ` and concatenated in the code. The latter is a cleaner approach but will have impact on ` big-top `.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              gsbiju Biju Nair
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: