[
https://issues.apache.org/jira/browse/HBASE-22414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869121#comment-16869121
]
Xiaolin Ha commented on HBASE-22414:
------------------------------------
[~wchevreuil] Thanks for your comments.
{quote}Yep, maybe mark those who failed in order to cleanup the state in meta
and ZK, before throwing exception upwards?
{quote}
I think in movement to RSGroup, group info is recorded in meta and zk firstly,
we should avoid regions on source group servers and still serving after calling
move tables or servers, but we couldn't change region state because region
state is updated by TRSP? So if a region on wrong RS is reassigned, the AM will
assign it to a correct RS according to RSGroup info.
> Interruption of moving regions in RSGroup will cause regions on wrong rs
> ------------------------------------------------------------------------
>
> Key: HBASE-22414
> URL: https://issues.apache.org/jira/browse/HBASE-22414
> Project: HBase
> Issue Type: Bug
> Components: rsgroup
> Affects Versions: 2.2.0
> Reporter: Xiaolin Ha
> Assignee: Xiaolin Ha
> Priority: Major
> Attachments: HBASE-22414.master.001.patch
>
>
> We bulk moving regions to target RSGroup, and each movement of region will
> submit a TRSP, but one TRSP encounters exception will make the whole movement
> action terminate. Later regions will not be moved to correct servers unless
> reassign.
> I think we can skip failed moved regions, and retry to move after all has
> been traversed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
