bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (JIRA)" <j...@apache.org>
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 21:38:50 GMT

    [ https://issues.apache.org/jira/browse/BIGTOP-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263995#comment-13263995
] 

Roman Shaposhnik commented on BIGTOP-566:
-----------------------------------------

Couple of comments:
  # we strongly discourage use of upstream scripts in Bigtop, so the invocation will be /usr/bin/flume-ng
--conf-file /etc/flume-ng/conf/flume.conf --conf /etc/flume-ng/conf --name agent
  # my understanding of flume is that it is an agent-based system with long running agents
on each node having a configuration that changes only when the agent gets restarted. If that's
the case then I'd like to propose that the details of --conf-file get hidden from the end
user. on a headless node the only configuration that flume can rely on would be a static set
of configs under /etc/flume/conf. And that's what should be used by the agent.

Please let me know if this makes sense.
                
> Flume NG pkg init script should allow user to customize the location of the conf dir
> ------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-566
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-566
>             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
>
>
> 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}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message