flume-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillermo Ortiz <konstt2...@gmail.com>
Subject Re: Flume doesn't stop the last agent when I modify the flume.conf
Date Thu, 26 Sep 2013 21:17:52 GMT
I think that I don't explain myself correctly.

Imagine that we have only one agent in our flume.conf. If I delete it from
my flume.conf, Flume doesn't call the stop method of my source, so I keep
producing data from Twitter (My source is a streaming of Twitter). Flume
detects that my agent doesn't exist anymore, that's right, but when you
delete the last one, it doesn't call the stop method.

If you do the same with two agents, I mean,,, you have the agents A and B,
and you delete the agent B, Flume calls the stop method of the source
(agent) B and reload the flume.conf, loading the configuration agent  and
the agent A.


2013/9/26 Hari Shreedharan <hshreedharan@cloudera.com>

>  You need to manually stop it. Flume does not stop itself if the agent
> name is not in the conf because the agent could pop up later if the conf is
> updated again.
> Thanks,
> Hari
> On Thursday, September 26, 2013 at 9:42 AM, Guillermo Ortiz wrote:
> I'm using Flume 1.4.0 with several agents, I have used the guide from
> Cloudera to connect with Twitter.
> I have created another class to modify the flume.conf,
> I have in the beginning two or three agents (for example), when I colud
> add or delete them, when I delete the last one, Flume doesn't stop that
> Agent, it doesn't call the stop method although it detects that it doesn't
> exist anymore in the flume.conf.
> How could I stop the agent?? I don't want to stop Flume because I could
> modify it and add another agent later.
> Thank you,
> Guillermo.

View raw message