[
https://issues.apache.org/jira/browse/BIGTOP-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291365#comment-14291365
]
jay vyas edited comment on BIGTOP-1581 at 1/26/15 1:56 AM:
-----------------------------------------------------------
*if* we decide to go with this, can we also add a {{smoke test}} for this
feature to demonstrate how it is actually exersized.
also, not clear what the *common* use case is as sean suggested, please
elaborate and thanks for the patch.
given the trend towards single purpose machines , *containers* and so on, i bet
the reasons to run multiple flume services per machine will be less relevant
,so might not be the best idea.
was (Author: jayunit100):
*if* we decide to go with this, can we also add a {{smoke test}} for this
feature to demonstrate how it is actually exersized.
also, not clear what the *common* use case is as sean suggested, please
elaborate and thanks for the 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: 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)
