bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (JIRA)" <>
Subject [jira] [Commented] (BIGTOP-566) Flume NG pkg init script should allow user to customize the location of the conf dir
Date Fri, 27 Apr 2012 22:08:50 GMT


Roman Shaposhnik commented on BIGTOP-566:

Will, thanks for the patch, but please answer my questions below. I still don't quite understand
what does this level of flexibility accomplish for the service script. I can understand why
explicit  invocations of bin/flume-ng could use this flexibility but that is already the case,
> Flume NG pkg init script should allow user to customize the location of the conf dir
> ------------------------------------------------------------------------------------
>                 Key: BIGTOP-566
>                 URL:
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>         Environment: all
>            Reporter: Will McQueen
>            Assignee: Bruno Mahé
>             Fix For: 0.4.0
>         Attachments: BIGTOP-566.patch, BIGTOP-566.patch
> A typical Flume NG invocation is:
>      bin/flume-ng --conf-file conf/  --conf conf --name
> ...and the corresponding invocation after installing the Flume NG bigtop package would
>      /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
> this:
>      FLUME_CONF_DIR=${FLUME_CONF_DIR:-/etc/flume-ng/conf}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message