[
https://issues.apache.org/jira/browse/HDFS-16600?focusedWorklogId=778447&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-778447
]
ASF GitHub Bot logged work on HDFS-16600:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jun/22 12:47
Start Date: 05/Jun/22 12:47
Worklog Time Spent: 10m
Work Description: slfan1989 commented on PR #4367:
URL: https://github.com/apache/hadoop/pull/4367#issuecomment-1146798609
@ZanderXu I found that some tests of Junit Test of HDFS (DN) sometimes
succeed and sometimes fail, but there is no way to judge whether it is related
to DeadLock. How do you judge the occurrence of DeadLock?
@MingXiangLi HDFS-16534 is a very big change, which will greatly help the
performance improvement of DN, but ZanderXu has already proposed 2 Jiras for
this change. Can you help to re-examine this HDFS-16534, if it is separate each
time The commit fixes pr, worried that it will bring more problems.
Issue Time Tracking
-------------------
Worklog Id: (was: 778447)
Time Spent: 1h 40m (was: 1.5h)
> 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 40m
> 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: [email protected]
For additional commands, e-mail: [email protected]
