[
https://issues.apache.org/jira/browse/HBASE-20860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16536935#comment-16536935
]
Ted Yu commented on HBASE-20860:
--------------------------------
{code}
+ private void cleanRITRegion(final MasterProcedureEnv env) {
{code}
cleanRITRegion -> cleanRITRegions (since two regions are being removed)
TestMasterAbortWhileMergingTable -> TestMasterAbortWhileMergingTables
{code}
+ HBaseClassTestRule.forClass(TestMergeTableRegionsProcedure.class);
{code}
Wrong class name.
> Merged region's RIT state may not be cleaned after master restart
> -----------------------------------------------------------------
>
> Key: HBASE-20860
> URL: https://issues.apache.org/jira/browse/HBASE-20860
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 3.0.0, 2.1.0, 2.0.1
> Reporter: Allan Yang
> Assignee: Allan Yang
> Priority: Major
> Fix For: 3.0.0, 2.1.0, 2.0.2
>
> Attachments: HBASE-20860.branch-2.0.patch
>
>
> In MergeTableRegionsProcedure, we issue UnassignProcedures to offline regions
> to merge. But if we restart master just after MergeTableRegionsProcedure
> finished these two UnassignProcedure and before it can delete their meta
> entries. The new master will found these two region is CLOSED but no
> procedures are attached to them. They will be regard as RIT regions and
> nobody will clean the RIT state for them later.
> A quick way to resolve this stuck situation in the production env is
> restarting master again, since the meta entries are deleted in
> MergeTableRegionsProcedure. Here, I offer a fix for this problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
