hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13145) TestNamespaceAuditor.testRegionMerge is flaky
Date Tue, 03 Mar 2015 22:30:05 GMT

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

Hudson commented on HBASE-13145:
--------------------------------

FAILURE: Integrated in HBase-TRUNK #6202 (See [https://builds.apache.org/job/HBase-TRUNK/6202/])
HBASE-13145 TestNamespaceAuditor.testRegionMerge is flaky (stack: rev 3897ab05a4630d6351853e17d82944fddd64e664)
* hbase-server/src/test/java/org/apache/hadoop/hbase/namespace/TestNamespaceAuditor.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java


> TestNamespaceAuditor.testRegionMerge is flaky
> ---------------------------------------------
>
>                 Key: HBASE-13145
>                 URL: https://issues.apache.org/jira/browse/HBASE-13145
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.0.0, 1.1.0
>            Reporter: zhangduo
>            Assignee: zhangduo
>             Fix For: 2.0.0, 1.1.0
>
>         Attachments: HBASE-13145.patch, HBASE-13145.patch
>
>
> Dig into the log
> https://builds.apache.org/job/HBase-TRUNK/6197/artifact/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.namespace.TestNamespaceAuditor-output.txt
> Seems a split operation which we expect to success is started before we finishing a merge
and cause an infinite sleep loop.
> I guess the problem is here
> {code:title=TestNamespaceAuditor.java}
>     // merge the two regions
>     admin.mergeRegions(hris.get(0).getEncodedNameAsBytes(),
>       hris.get(1).getEncodedNameAsBytes(), false);
>     
>     while (admin.getTableRegions(tableTwo).size() == initialRegions) {
>       Thread.sleep(100);
>     }
> {code}
> I guess that during a merge, we can get more region count than before because we first
online the new region and then offline the two old regions.
> So change it to admin.getTableRegions(tableTwo).size() != initialRegions - 1 may work.
> And we can modify the while loop to use Waiter.waitFor which can provide more useful
information when test failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message