[
https://issues.apache.org/jira/browse/HBASE-20881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572508#comment-16572508
]
Duo Zhang commented on HBASE-20881:
-----------------------------------
It seems that I have to deal with the DisableTableProcedure...
I added a TODO in AssignmentManager that when creating an UnassignProcedure
there could already have a TRSP and plan to do it in a follow-on issue. But it
seems that it will be easily produced in UT... Will be back later.
[~stack] Could you please take a look at the current approach sir? It aims to
solve the conflicts for split/merge and assign/unassign/move.
Thanks.
> 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
> Components: amv2, proc-v2
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-20881-v1.patch, HBASE-20881-v2.patch,
> HBASE-20881-v3.patch, HBASE-20881-v4.patch, HBASE-20881-v4.patch,
> HBASE-20881-v5.patch, HBASE-20881.patch
>
>
> 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)
