[
https://issues.apache.org/jira/browse/BIGTOP-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288871#comment-14288871
]
YoungWoo Kim edited comment on BIGTOP-1581 at 1/23/15 7:05 AM:
---------------------------------------------------------------
[~gsbiju] Thanks for the patch. Looks good to me but a minor suggestion here.
In real world, I added flume monitoring[1] for each agent. It looks like '...
-Dflume.monitoring.type=http -Dflume.monitoring.port=34545 ...'. It would be
nice if we can enable monitoring for Flume in the init script.
1. http://flume.apache.org/FlumeUserGuide.html#monitoring
was (Author: warwithin):
[~gsbiju] Thanks for the patch. Looks good to me but a minor suggestion here.
In real world, I added flume monitoring[1] for each agent. It looks like '...
-Dflume.monitoring.type=http -Dflume.monitoring.port=34545 ...'. It would be
nice if we can use flume-monitoring in the init script.
1. http://flume.apache.org/FlumeUserGuide.html#monitoring
> 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)
