[
https://issues.apache.org/jira/browse/HBASE-19026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207831#comment-16207831
]
Ted Yu commented on HBASE-19026:
--------------------------------
In successful run, we should see something like this:
{code}
2017-10-17 08:22:25,884 DEBUG [ProcExecWrkr-1] locking.LockProcedure(243):
TIMED OUT pid=14, state=RUNNABLE;
org.apache.hadoop.hbase.master.locking.LockProcedure,
namespace=namespace, type=EXCLUSIVE
{code}
Since LockProcedure#execute() times out the lock whose heartbeat has expired,
the patch gives ProcedureExecutor more time for running the execute() method.
> TestLockProcedure#testRemoteNamespaceLockRecovery fails in master
> -----------------------------------------------------------------
>
> Key: HBASE-19026
> URL: https://issues.apache.org/jira/browse/HBASE-19026
> Project: HBase
> Issue Type: Test
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 19026.v1.txt
>
>
> This can be reproduced locally:
> {code}
> testRemoteNamespaceLockRecovery(org.apache.hadoop.hbase.master.locking.TestLockProcedure)
> Time elapsed: 8.722 sec <<< FAILURE!
> java.lang.AssertionError: expected:<UNLOCKED> but was:<LOCKED>
> at
> org.apache.hadoop.hbase.master.locking.TestLockProcedure.sendHeartbeatAndCheckLocked(TestLockProcedure.java:219)
> at
> org.apache.hadoop.hbase.master.locking.TestLockProcedure.testRemoteLockRecovery(TestLockProcedure.java:401)
> at
> org.apache.hadoop.hbase.master.locking.TestLockProcedure.testRemoteNamespaceLockRecovery(TestLockProcedure.java:415)
> {code}
> See also
> https://builds.apache.org/job/HBase-TRUNK_matrix/3902/jdk=JDK%201.8%20(latest),label=Hadoop/testReport/org.apache.hadoop.hbase.master.locking/TestLockProcedure/testRemoteNamespaceLockRecovery/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
