[
https://issues.apache.org/jira/browse/HBASE-20881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561107#comment-16561107
]
Duo Zhang commented on HBASE-20881:
-----------------------------------
There are some progress. And I think this can only go into 2.2+, as
RegionTransitionProcedure is part of the AssignmentManager, if we change to use
another procedure to replace it, then we need to modify the code in
AssignmentManager, and it will be conflict with the old code with
RegionTransitionProcedure.
And the solution will be simple, disable balancer before restarting master with
the new code, so we will not have RegionTransitionProcedure when restarting,
then everything will be OK. And we could add a check when loading procedures,
if there are AssignProcedure/UnassignProcedure, then we abort and tell users to
restart with the old code first to finish these procedures.
But I think this maybe too much a patch release, so let's do it in 2.2+.
> Introduce a region transition procedure to handle all the state transition
> for a region
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-20881
> URL: https://issues.apache.org/jira/browse/HBASE-20881
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
>
> Now have an AssignProcedure, an UnssignProcedure, and also a
> MoveRegionProcedure which schedules an AssignProcedure and an
> UnssignProcedure to move a region. This makes the logic a bit complicated, as
> MRP is not a RIT, so when SCP can not interrupt it directly...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
