Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.4.0
-
None
-
None
-
all
Description
A typical Flume NG invocation is:
bin/flume-ng --conf-file conf/flume-conf.properties.template --conf conf --name agent1
...and the corresponding invocation after installing the Flume NG bigtop package would be:
/usr/lib/flume-ng/bin/flume-ng --conf-file /etc/flume-ng/conf/flume.conf --conf /etc/flume-ng/conf --name agent
The Flume NG init script, installed as part of Bigtop Flume NG, allows us to modify:
1) the --conf-file value (via FLUME_CONF_FILE)
2) the --name value (via FLUME_AGENT_NAME)
...but not the --conf value. So the user loses some flexibility when using Bigtop Flume NG over Apache Flume NG.
I recommend that the /etc/init.d/flume-ng-agent script be modified to allow the user to set FLUME_CONF_DIR. That is, in this init script, please change this:
FLUME_CONF_DIR=/etc/flume-ng/conf
..to this:
FLUME_CONF_DIR=${FLUME_CONF_DIR:-/etc/flume-ng/conf}