You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flume.apache.org by "Hari Shreedharan (JIRA)" <ji...@apache.org> on 2013/03/14 05:52:17 UTC

[jira] [Commented] (FLUME-1930) Inflights should clean up executors on close.

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

Hari Shreedharan commented on FLUME-1930:
-----------------------------------------

[~juhani@ninja.co.jp] It looks like my analysis was correct. The thread rename happened in this patch itself (inflights-sync-thread). Interestingly I actually call shutdownNow on the executor, which should kill the executor anyway (since it is simply waiting for more events). Did you try waiting for some time (like a couple minutes?). I think it should just die. 
                
> Inflights should clean up executors on close.
> ---------------------------------------------
>
>                 Key: FLUME-1930
>                 URL: https://issues.apache.org/jira/browse/FLUME-1930
>             Project: Flume
>          Issue Type: Bug
>            Reporter: Hari Shreedharan
>            Assignee: Hari Shreedharan
>            Priority: Minor
>         Attachments: FLUME-1930.patch, stack-dump
>
>
> Looks like the JVM hang Juhani saw in FLUME-1929 was due to the fact that InflightEventWrapper has executors that are not cleaned up

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira