[
https://issues.apache.org/jira/browse/HBASE-22733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-22733.
---------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.1.6
2.2.1
2.0.6
2.3.0
3.0.0
Pushed to branch-2.0+. Nice patch [~Xiaolin Ha]. Thank you for fixing flakey
test.
> TestSplitTransactionOnCluster.testMasterRestartAtRegionSplitPendingCatalogJanitor
> is flakey
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-22733
> URL: https://issues.apache.org/jira/browse/HBASE-22733
> Project: HBase
> Issue Type: Bug
> Reporter: Xiaolin Ha
> Assignee: Xiaolin Ha
> Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6
>
> Attachments: test -
> testMasterRestartAtRegionSplitPendingCatalogJanitor [Jenkins].txt
>
>
> RITs will lead to CatalogJanitor not running, and then parent region will not
> be cleaned.
> As a result, the last assertion of checking if parent region is null will
> fail.
> {quote}
> h3. Error Message
> expected:<null> but was:<maven-jdk8-551kz,45127,1563877982046>
> h3. Stacktrace
> java.lang.AssertionError: expected:<null> but
> was:<maven-jdk8-551kz,45127,1563877982046> at
> org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster.testMasterRestartAtRegionSplitPendingCatalogJanitor(TestSplitTransactionOnCluster.java:577){quote}
> Currently, the case is only waiting for master be active while not care about
> RITs completion when master starts up.
> Failed test results is attached. We can see CatalogJanitor chore run failed
> log in it,
> {quote}2019-07-23 18:34:03,241 INFO [Time-limited test]
> regionserver.TestSplitTransactionOnCluster(572): Starting run of
> CatalogJanitor 2019-07-23 18:34:03,241 WARN [Time-limited test]
> master.CatalogJanitor(119): CatalogJanitor is disabled! Enabled=true,
> maintenanceMode=false,
> am=org.apache.hadoop.hbase.master.assignment.AssignmentManager@1ce25bee,
> metaLoaded=true, hasRIT=true clusterShutDown=false
> {quote}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
