[jira] [Commented] (BIGTOP-1581) Allow multiple Flume agents to be executed as a service using Bigtop init.d script

["Biju Nair (JIRA)" <ji...@apache.org>]

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

Biju Nair commented on BIGTOP-1581:
-----------------------------------

One approach we are taking is to 
- Allow users to pass an agent name to perform service request (start|stop|restart|...)
{{service flume-agent start agent-name}}
- flume-agent-name.conf is expected to be stored in $FLUME_CONF_DIR (default /etc/flume/conf directory) for the request to be successful
- If user doesn't provide an agent-name for a service request (start|stop|restart|...) then service action is taken on all the agents with conf file in FLUME_CONF_DIR. 

Attached is the updated init.d script. If this approach is useful to broader community let me know and I can provide a patch.

> 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: 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)