Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3BF04D463 for ; Tue, 24 Jul 2012 18:31:35 +0000 (UTC) Received: (qmail 77397 invoked by uid 500); 24 Jul 2012 18:31:35 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 77350 invoked by uid 500); 24 Jul 2012 18:31:35 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 77341 invoked by uid 99); 24 Jul 2012 18:31:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jul 2012 18:31:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id D61D8142838 for ; Tue, 24 Jul 2012 18:31:34 +0000 (UTC) Date: Tue, 24 Jul 2012 18:31:34 +0000 (UTC) From: "Suresh Srinivas (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1102379818.97098.1343154694879.JavaMail.jiratomcat@issues-vm> In-Reply-To: <582843225.96420.1343149415421.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HDFS-3718) Datanode won't shutdown because of runaway DataBlockScanner thread MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421622#comment-13421622 ] Suresh Srinivas commented on HDFS-3718: --------------------------------------- There is no specific reason for that order. We should set DataNode#shouldRun to false before other shutdown calls. > 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 > Priority: Critical > Fix For: 3.0.0, 2.2.0-alpha > > > 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