Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 30 Nov 2015 15:37:11 +0000 (UTC)
From: "Heng Chen (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12916989.1448897793000.221949.1448897831073@Atlassian.JIRA>
In-Reply-To: <JIRA.12916989.1448897793000@Atlassian.JIRA>
References: <JIRA.12916989.1448897793000@Atlassian.JIRA>
 <JIRA.12916989.1448897793251@arcas>
Subject: [jira] [Created] (HBASE-14897)
 TestTableLockManager.testReapAllTableLocks is flakey
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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)