[ https://issues.apache.org/jira/browse/HDFS-16600?focusedWorklogId=778436&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-778436 ]
ASF GitHub Bot logged work on HDFS-16600: ----------------------------------------- Author: ASF GitHub Bot Created on: 05/Jun/22 09:27 Start Date: 05/Jun/22 09:27 Worklog Time Spent: 10m Work Description: MingXiangLi commented on PR #4367: URL: https://github.com/apache/hadoop/pull/4367#issuecomment-1146772397 @ZanderXu LGTM.The core logic in HDFS-16534 is change block pool write lock to read lock and add volume lock for each replica under this block pool.And we didn't change this method in HDFS-16534 because it's not a heavy call. So this commit is makes sense to me. Issue Time Tracking ------------------- Worklog Id: (was: 778436) Time Spent: 1h 20m (was: 1h 10m) > Deadlock on DataNode > -------------------- > > Key: HDFS-16600 > URL: https://issues.apache.org/jira/browse/HDFS-16600 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: ZanderXu > Assignee: ZanderXu > Priority: Major > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > The UT > org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.testSynchronousEviction > failed, because happened deadlock, which is introduced by > [HDFS-16534|https://issues.apache.org/jira/browse/HDFS-16534]. > DeadLock: > {code:java} > // org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.createRbw line 1588 > need a read lock > try (AutoCloseableLock lock = lockManager.readLock(LockLevel.BLOCK_POOl, > b.getBlockPoolId())) > // org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.evictBlocks line > 3526 need a write lock > try (AutoCloseableLock lock = lockManager.writeLock(LockLevel.BLOCK_POOl, > bpid)) > {code} -- This message was sent by Atlassian Jira (v8.20.7#820007) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org