hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Heng Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14897) TestTableLockManager.testReapAllTableLocks is flakey
Date Wed, 09 Dec 2015 06:32:10 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048138#comment-15048138
] 

Heng Chen commented on HBASE-14897:
-----------------------------------

https://builds.apache.org/view/H-L/view/HBase/job/HBase-Trunk_matrix/540/jdk=latest1.8,label=Hadoop/testReport/org.apache.hadoop.hbase.master/TestTableLockManager/testReapAllTableLocks/history/

It seems good now.

> 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
>         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
(v6.3.4#6332)

Mime
View raw message