[
https://issues.apache.org/jira/browse/HDFS-9445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035016#comment-15035016
]
Mingliang Liu commented on HDFS-9445:
-------------------------------------
The _bposLock --> FSDatasetLock_ locking order looks good to me.
The {{TestDirectoryScanner#testThrottle()}} is flaky and is tracked by
[HDFS-9300]. The {{org.apache.hadoop.hdfs.server.namenode.TestMetaSave}} fails
consistently on {{trunk}} branch and is considered a bug (newly filed
[HDFS-9493] to track this). All other failing tests can not reproduce locally
(both Gentoo Linux and Mac).
[~kihwal], the {{TestEditLogTailer#testNN1TriggersLogRolls}} is known to fail
with bind exception and is tracked by [HDFS-9444]. I don't think it is related
to this patch anyway.
+1 (non-binding)
> Deadlock in datanode
> --------------------
>
> 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
> Attachments: 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)
