You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2013/01/31 22:39:15 UTC
[jira] [Updated] (HBASE-7733) Fix flaky
TestZKProcedure.testMultiCohortWithMemberTimeoutDuringPrepare
[ https://issues.apache.org/jira/browse/HBASE-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh updated HBASE-7733:
----------------------------------
Description:
Sometimes this test fails with this error message:
{code}
Wanted but not invoked:
procedure.sendGlobalBarrierComplete();
-> at org.apache.hadoop.hbase.procedure.TestZKProcedure.waitAndVerifyProc(TestZKProcedure.java:344)
However, there were other interactions with this mock:
-> at org.apache.hadoop.hbase.procedure.TestZKProcedure.testMultiCohortWithMemberTimeoutDuringPrepare(TestZKProcedure.java:306)
-> at org.apache.hadoop.hbase.procedure.TestZKProcedure.testMultiCohortWithMemberTimeoutDuringPrepare(TestZKProcedure.java:311)
-> at org.apache.hadoop.hbase.procedure.Procedure.call(Procedure.java:190)
-> at org.apache.hadoop.hbase.procedure.Procedure.call(Procedure.java:190)
-> at org.apache.hadoop.hbase.procedure.Procedure.call(Procedure.java:190)
-> at org.apache.hadoop.hbase.procedure.Procedure.call(Procedure.java:190)
-> at org.apache.hadoop.hbase.procedure.ProcedureCoordinator.abortProcedure(ProcedureCoordinator.java:173)
-> at org.apache.hadoop.hbase.procedure.TestZKProcedure.waitAndVerifyProc(TestZKProcedure.java:337)
{code}
was:
Sometimes this test fails with this error message:
{code}
Wanted but not invoked: procedure.sendGlobalBarrierComplete(); -> at org.apache.hadoop.hbase.procedure.TestZKProcedure.waitAndVerifyProc(TestZKProcedure.java:344) However, there were other interactions with this mock: -> at org.apache.hadoop.hbase.procedure.TestZKProcedure.testMultiCohortWithMemberTimeoutDuringPrepare(TestZKProcedure.java:306) -> at org.apache.hadoop.hbase.procedure.TestZKProcedure.testMultiCohortWithMemberTimeoutDuringPrepare(TestZKProcedure.java:311) -> at org.apache.hadoop.hbase.procedure.Procedure.call(Procedure.java:205) -> at org.apache.hadoop.hbase.procedure.Procedure.call(Procedure.java:205) -> at org.apache.hadoop.hbase.procedure.ProcedureCoordinator.memberAcquiredBarrier(ProcedureCoordinator.java:228) -> at org.apache.hadoop.hbase.procedure.ProcedureCoordinator.memberAcquiredBarrier(ProcedureCoordinator.java:228) -> at org.apache.hadoop.hbase.procedure.ProcedureCoordinator.abortProcedure(ProcedureCoordinator.java:183) -> at org.apache.hadoop.hbase.procedure.TestZKProcedure.waitAndVerifyProc(TestZKProcedure.java:337)
{code}
> Fix flaky TestZKProcedure.testMultiCohortWithMemberTimeoutDuringPrepare
> -----------------------------------------------------------------------
>
> Key: HBASE-7733
> URL: https://issues.apache.org/jira/browse/HBASE-7733
> Project: HBase
> Issue Type: Sub-task
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
>
> Sometimes this test fails with this error message:
> {code}
> Wanted but not invoked:
> procedure.sendGlobalBarrierComplete();
> -> at org.apache.hadoop.hbase.procedure.TestZKProcedure.waitAndVerifyProc(TestZKProcedure.java:344)
> However, there were other interactions with this mock:
> -> at org.apache.hadoop.hbase.procedure.TestZKProcedure.testMultiCohortWithMemberTimeoutDuringPrepare(TestZKProcedure.java:306)
> -> at org.apache.hadoop.hbase.procedure.TestZKProcedure.testMultiCohortWithMemberTimeoutDuringPrepare(TestZKProcedure.java:311)
> -> at org.apache.hadoop.hbase.procedure.Procedure.call(Procedure.java:190)
> -> at org.apache.hadoop.hbase.procedure.Procedure.call(Procedure.java:190)
> -> at org.apache.hadoop.hbase.procedure.Procedure.call(Procedure.java:190)
> -> at org.apache.hadoop.hbase.procedure.Procedure.call(Procedure.java:190)
> -> at org.apache.hadoop.hbase.procedure.ProcedureCoordinator.abortProcedure(ProcedureCoordinator.java:173)
> -> at org.apache.hadoop.hbase.procedure.TestZKProcedure.waitAndVerifyProc(TestZKProcedure.java:337)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira