[
https://issues.apache.org/jira/browse/BIGTOP-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261684#comment-14261684
]
Sean Mackrory commented on BIGTOP-1581:
---------------------------------------
This is reminiscent of BIGTOP-732 - where I essentially did the same thing for
HBase RegionServers as running multiple RegionServers per DataNode was
sometimes recommended. It may be helpful to browse that thread and see some of
the edge cases and complexities that eventually went into that patch.
Other than the HBase devs who originally suggested that change, I don't know
how commonly it's used and it did add a lot of complexity that's going to make
things hard if / when we start supporting systemd or another SysV-init
replacement - so I would personally be a little cautious about doing this for
another service. But I wouldn't -1 it...
> 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)
