Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 24 Aug 2013 02:01:53 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12665310.1377287233580.27166.1377309713198@arcas>
In-Reply-To: <JIRA.12665310.1377287233580@arcas>
References: <JIRA.12665310.1377287233580@arcas>
Subject: [jira] [Commented] (HBASE-9324)
 TestProcedureMember#testMemberCommitException, testSimpleRun &
 testMemberCommitCommsFailure are flaky on Suse OS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HBASE-9324:
-------------------------------

FAILURE: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #696 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/696/])
HBASE-9324: TestProcedureMember#testMemberCommitException, testSimpleRun & testMemberCommitCommsFailure are flaky on Suse OS (jeffreyz: rev 1517066)
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/procedure/ProcedureMember.java

                
> 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
>             Fix For: 0.95.2, 0.96.0
>
>         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