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 D4F36185EB for ; Mon, 4 Jan 2016 15:16:40 +0000 (UTC) Received: (qmail 12642 invoked by uid 500); 4 Jan 2016 15:16:40 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 12546 invoked by uid 500); 4 Jan 2016 15:16:40 -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 12177 invoked by uid 99); 4 Jan 2016 15:16:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jan 2016 15:16:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 048602C1F5D for ; Mon, 4 Jan 2016 15:16:40 +0000 (UTC) Date: Mon, 4 Jan 2016 15:16:40 +0000 (UTC) From: "Kihwal Lee (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-9445) Datanode may deadlock while handling a bad volume 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-9445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081254#comment-15081254 ] Kihwal Lee commented on HDFS-9445: ---------------------------------- The branch build failure might be related to HDFS-8346. We might want to pull that in to branch-2.6 and branch-2.7. > Datanode may deadlock while handling a bad volume > ------------------------------------------------- > > Key: HDFS-9445 > URL: https://issues.apache.org/jira/browse/HDFS-9445 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 2.7.2 > Reporter: Kihwal Lee > Assignee: Walter Su > Priority: Blocker > Fix For: 3.0.0, 2.7.2, 2.6.4 > > Attachments: HDFS-9445-branch-2.6.02.patch, HDFS-9445-branch-2.6_02.patch, HDFS-9445.00.patch, HDFS-9445.01.patch, HDFS-9445.02.patch > > > {noformat} > Found one Java-level deadlock: > ============================= > "DataXceiver for client DFSClient_attempt_xxx at /1.2.3.4:100 [Sending block BP-xxxxx:blk_123_456]": > waiting to lock monitor 0x00007f77d0731768 (object 0x00000000d60d9930, a org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl), > which is held by "Thread-565" > "Thread-565": > waiting for ownable synchronizer 0x00000000d55613c8, (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync), > which is held by "DataNode: heartbeating to my-nn:8020" > "DataNode: heartbeating to my-nn:8020": > waiting to lock monitor 0x00007f77d0731768 (object 0x00000000d60d9930, a org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl), > which is held by "Thread-565" > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)