You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/08/23 21:57:52 UTC
[jira] [Commented] (HBASE-9324)
TestProcedureMember#testMemberCommitException, testSimpleRun &
testMemberCommitCommsFailure are flaky on Suse OS
[ https://issues.apache.org/jira/browse/HBASE-9324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748934#comment-13748934 ]
stack commented on HBASE-9324:
------------------------------
+1 for 0.95 and trunk.
> TestProcedureMember#testMemberCommitException, testSimpleRun & testMemberCommitCommsFailure are flaky on Suse OS
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-9324
> URL: https://issues.apache.org/jira/browse/HBASE-9324
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: Jeffrey Zhong
> Assignee: Jeffrey Zhong
> Attachments: hbase-9324.patch
>
>
> The failures are due to a race condition that sub procedure could finish before the sub procedure is added into internal map ProcedureMember#subprocs. Below is the related code:
> {code}
> future = this.pool.submit(subproc);
> synchronized (subprocs) {
> subprocs.put(procName, subproc);
> }
> {code}
> As you can see the above, that subproc could finish before {code}subprocs.put(procName, subproc);{code}. Therefore, the test will fail with the following error message:
> {code}
> procedure.ProcedureMember(189): Unexpected reached glabal barrier message for Sub-Procedure 'some op'
> {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