flume-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cameron Gandevia <cgande...@gmail.com>
Subject Re: Regarding recent InterruptedException issues.
Date Thu, 20 Oct 2011 18:29:20 GMT
Interesting. I will rollback to the same revision and test with my
configuration. Thanks for the heads up.

On Wed, Oct 19, 2011 at 11:54 PM, Mingjie Lai <mjlai09@gmail.com> wrote:

> Hi.
> As some ones on the list, I also noticed the InterruptedException issue of
> DirectDriver, but under different situation. If I reconfigure a node, the
> node always raises some InterruptedException in log. It seems the node's
> source.close() not getting called at all. It can explain others'
> observation, such as InterruptedExc of rollsink and colletorSink, since they
> all keep closing source/sink once a while. If a Driver cannot see the thread
> exiting gracefully, it will force the thread to exit by interrupt, which can
> bring unexpected behavior for different source/sinks.
> It might be brought by a patch of Flume-596 which is a big refactor of
> Driver. I rolled the source code back to 036a5106a0b15e25029e458349d9e6**bf2142ea21,
> but cannot reproduce the issue. Then I can see it again if cherry-picked
> Flume-596.
> I opened https://issues.apache.org/**jira/browse/FLUME-808<https://issues.apache.org/jira/browse/FLUME-808>for
detail discussion.
> Thanks,
> Mingjie


Cameron Gandevia

View raw message