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

Biju Nair edited comment on BIGTOP-1581 at 1/28/15 8:27 PM:
------------------------------------------------------------

[~jayunit100], from a quick look at the smoke-test, here is a rough outline on 
modifying the existing smoke test for Flume

- Change the file name to flume-agent.conf 
[here|https://github.com/apache/bigtop/blob/master/bigtop-tests/smoke-tests/flume/TestFlumeNG.groovy#L75].
- Create flume-env.sh in /etc/flume/conf and {{export FLUME_JAVAOPTS}} with 
[value|https://github.com/apache/bigtop/blob/master/bigtop-tests/smoke-tests/flume/TestFlumeNG.groovy#L83]
- Instead of using flume-ng script 
[here|https://github.com/apache/bigtop/blob/master/bigtop-tests/smoke-tests/flume/TestFlumeNG.groovy#L80-L84]
 user *service* command to start flume. {{service flume-agent start}}. The 
assumption is that sysvinit is used and flume-agent service is enabled.
- During 
[teardown|https://github.com/apache/bigtop/blob/master/bigtop-tests/smoke-tests/flume/TestFlumeNG.groovy#L80-L84]
 perform {{service flume-agent stop}}

If something is overlooked let me know. 

On the second question, I will be happy to help with maintaining the code. 


was (Author: gsbiju):
[~jayunit100], from a quick look at the smoke-test, here is a rough outline on 
modifying the existing smoke test for Flume

- Change the file name to flume-agent.conf 
[here|https://github.com/apache/bigtop/blob/master/bigtop-tests/smoke-tests/flume/TestFlumeNG.groovy#L75].
- Create flume-env.sh in /etc/flume/conf and export FLUME_JAVAOPTS with 
[value|https://github.com/apache/bigtop/blob/master/bigtop-tests/smoke-tests/flume/TestFlumeNG.groovy#L83]
- Instead of using flume-ng script 
[here|https://github.com/apache/bigtop/blob/master/bigtop-tests/smoke-tests/flume/TestFlumeNG.groovy#L80-L84]
 user *service* command to start flume. `` service flume-agent start ``. The 
assumption is that sysvinit is used and flume-agent service is enabled.
- During 
[teardown|https://github.com/apache/bigtop/blob/master/bigtop-tests/smoke-tests/flume/TestFlumeNG.groovy#L80-L84]
 perform *service flume-agent stop* 

If something is overlooked let me know. 

On the second question, I will be happy to help with maintaining the code. 

> 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, BIGTOP-1581-1.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)

Reply via email to