You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Biju Nair (JIRA)" <ji...@apache.org> on 2014/12/24 16:08:13 UTC
[jira] [Updated] (BIGTOP-1581) Allow multiple Flume agents to be
executed as a service using Bigtop init.d script
[ https://issues.apache.org/jira/browse/BIGTOP-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Biju Nair updated BIGTOP-1581:
------------------------------
Description: 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. (was: 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 start them it will help many installations.)
> 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
>
>
> 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)