hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yang Jiandan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3718) Datanode won't shutdown because of runaway DataBlockScanner thread
Date Mon, 19 Aug 2013 02:44:48 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743494#comment-13743494

Yang Jiandan commented on HDFS-3718:

Why interrupt is missing?
I found every place to throw InterruptedException has called Thread.interrupt to set interrupt
> Datanode won't shutdown because of runaway DataBlockScanner thread
> ------------------------------------------------------------------
>                 Key: HDFS-3718
>                 URL: https://issues.apache.org/jira/browse/HDFS-3718
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: 2.0.1-alpha
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>            Priority: Critical
>             Fix For: 0.23.3, 2.0.2-alpha
>         Attachments: hdfs-3718.patch.txt
> Datanode sometimes does not shutdown because the block pool scanner thread keeps running.
It prints out "Starting a new period" every five seconds, even after {{shutdown()}} is called.
 Somehow the interrupt is missed.
> {{DataBlockScanner}} will also terminate if {{datanode.shouldRun}} is false, but in {{DataNode#shutdown}},
{{DataBlockScanner#shutdown()}} is invoked before it is being set to false.
> Is there any reason why {{datanode.shouldRun}} is set to false later? 

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

View raw message