[
https://issues.apache.org/jira/browse/HDFS-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434680#comment-13434680
]
Hudson commented on HDFS-3718:
------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #2642 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2642/])
HDFS-3718. Datanode won't shutdown because of runaway DataBlockScanner
thread (Kihwal Lee via daryn) (Revision 1373090)
Result = FAILURE
daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1373090
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java
> 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: data-node
> Affects Versions: 2.0.1-alpha
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Priority: Critical
> Fix For: 0.23.3, 2.1.0-alpha, 3.0.0, 2.2.0-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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
