hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "huaxiang sun (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15206) Flakey testSplitDaughtersNotInMeta test
Date Tue, 02 Feb 2016 21:31:39 GMT

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

huaxiang sun commented on HBASE-15206:

Thanks [~jon@cloudera.com] for reviewing. For 1), I think it may be case by case. 

For 2), 
Even if catalog janitor wakes up and cleans up the parent region, hbase fsck still works (from
the unittest result). The issue is that it still expects the parent region be in the metatable
after hbase fsck, which could be cleaned up by the catalog janitor. Either we disable the
CatalogJanitor or remove this assert (I do not understand why this assert for parent region
is required after split).

      Result result = meta.get(get);
      assertNotNull(MetaTableAccessor.getHRegionInfo(result)); // make sure the parent region
info still exists in meta table, failed here.

> Flakey testSplitDaughtersNotInMeta test
> ---------------------------------------
>                 Key: HBASE-15206
>                 URL: https://issues.apache.org/jira/browse/HBASE-15206
>             Project: HBase
>          Issue Type: Bug
>          Components: flakey
>            Reporter: huaxiang sun
>            Assignee: huaxiang sun
>            Priority: Minor
>         Attachments: HBASE-15206-001.patch
> Run into the following failure with hbase 1.0.0.
> Stacktrace
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertNotNull(Assert.java:712)
> at org.junit.Assert.assertNotNull(Assert.java:722)
> at org.apache.hadoop.hbase.util.TestHBaseFsck.testSplitDaughtersNotInMeta(TestHBaseFsck.java:1723)
> From the log, the ntp issue caused clock skew and it woke up CatalogJanitor earlier.
The CatalogJanitor cleaned up the parent region. It could happen with master branch as well.
The fix is to disable CatalogJanitor to make sure this will not happen.

This message was sent by Atlassian JIRA

View raw message