You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Heng Chen (JIRA)" <ji...@apache.org> on 2015/11/30 16:37:11 UTC
[jira] [Created] (HBASE-14897)
TestTableLockManager.testReapAllTableLocks is flakey
Heng Chen created HBASE-14897:
---------------------------------
Summary: TestTableLockManager.testReapAllTableLocks is flakey
Key: HBASE-14897
URL: https://issues.apache.org/jira/browse/HBASE-14897
Project: HBase
Issue Type: Bug
Reporter: Heng Chen
It comes from email list which [~stack] post.
This is the some relates QA information.
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Trunk_matrix/512/jdk=latest1.8,label=Hadoop/testReport/org.apache.hadoop.hbase.master/TestTableLockManager/testReapAllTableLocks/
The reason is here.
{code}
writeLocksObtained.await();
writeLocksAttempted.await();
{code}
writeLocksAttempted maybe count down to 0 before created node on ZK, and main thread will go on to run lockManager.reapWriteLocks(), And after that node was created on ZK, so relates lock acquire will timeout.
I upload a patch which can reproduce this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)