[
https://issues.apache.org/jira/browse/HBASE-20860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16536977#comment-16536977
]
stack commented on HBASE-20860:
-------------------------------
bq. ...after MergeTableRegionsProcedure finished these two UnassignProcedure
and before it can delete their meta entries.
Are we talking the MERGE_TABLE_REGIONS_UPDATE_META step [~allan163] ? If Master
dies, do we not rerun this step?
Or, we do rerun this step but the load meta that is done by the new master
registers the CLOSED regions as RIT ... and they are never cleared.
Would it be better not registering CLOSED regions as RIT when new master loads
the meta table (as per [~Apache9]). Thanks [~allan163].
> 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)
