[
https://issues.apache.org/jira/browse/BIGTOP-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290193#comment-14290193
]
Biju Nair edited comment on BIGTOP-1581 at 1/23/15 11:17 PM:
-------------------------------------------------------------
[~warwithin], thanks for the feedback. Will it not be better to set these
parameters in flume-env.sh which is sourced by flume-ng script either in either
in $JAVA_OPTS or $FLUME_OPTS variables. This will also keep the init.d simple
and straight forward while maintaining consistency of single location where
parameters for flume-ng need to be set/defined.
was (Author: gsbiju):
@youngwookim, thanks for the feedback. Will it not be better to set these
parameters in flume-env.sh which is sourced by flume-ng script either in either
in $JAVA_OPTS or $FLUME_OPTS variables. This will also keep the init.d simple
and straight forward while maintaining consistency of single location where
parameters for flume-ng need to be set/defined.
> Allow multiple Flume agents to be executed as a service using Bigtop init.d
> script
> ----------------------------------------------------------------------------------
>
> Key: BIGTOP-1581
> URL: https://issues.apache.org/jira/browse/BIGTOP-1581
> Project: Bigtop
> Issue Type: Improvement
> Components: Init scripts
> Affects Versions: 0.6.0, 0.7.0, 0.8.0
> Reporter: Biju Nair
> Labels: features
> Fix For: backlog, 0.8.0, 0.9.0, 1.0.0
>
> Attachments: BIGTOP-1581-0.patch, flume-agent.init
>
>
> Using the current init.d script only one Flume agent can be managed as a
> service. In practice there will be more than one Flume agent on a node which
> need be managed. If the init.d script can be improved to accept a agent name
> for the service requests (start|stop|restart|...) and manage them it will
> help many installations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
