You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2019/02/01 19:55:00 UTC
[jira] [Updated] (HBASE-14897)
TestTableLockManager.testReapAllTableLocks is flakey
[ https://issues.apache.org/jira/browse/HBASE-14897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-14897:
-----------------------------------
Fix Version/s: (was: 1.5.0)
> TestTableLockManager.testReapAllTableLocks is flakey
> ----------------------------------------------------
>
> Key: HBASE-14897
> URL: https://issues.apache.org/jira/browse/HBASE-14897
> Project: HBase
> Issue Type: Bug
> Reporter: Heng Chen
> Assignee: Heng Chen
> Priority: Major
> Fix For: 1.3.2, 1.4.3, 2.0.0, 1.2.7
>
> Attachments: HBASE-14897.patch, reproduce.patch
>
>
> 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
(v7.6.3#76005)