[
https://issues.apache.org/jira/browse/HBASE-22642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885741#comment-16885741
]
Xu Cang edited comment on HBASE-22642 at 7/16/19 1:03 AM:
----------------------------------------------------------
This is an interesting angle to look at this issue. thanks.
And I don't see any other overheads beside the one you mentioned. [~Xiaolin Ha]
Can you fix the conflict and let hadoopQA run it.
was (Author: xucang):
this is an interesting angle to look at this issue. thanks.
can you elaborate on this comment "repeatedly moving tables/servers to a group
might not make regions be moved repeatedly,"? [~Xiaolin Ha]
> Make move operations of RSGroup idempotent
> ------------------------------------------
>
> Key: HBASE-22642
> URL: https://issues.apache.org/jira/browse/HBASE-22642
> Project: HBase
> Issue Type: Bug
> Components: rsgroup
> Reporter: Xiaolin Ha
> Assignee: Xiaolin Ha
> Priority: Major
>
> Currently, when moving tables or servers to a group, only groupInfo is
> checked. And in RSGroup implementation, groupinfo is written to disk before
> regions movements are done. If there are some problems caused move regions
> abort, some regions will be on wrong regionservers. What's the worse, retry
> the move operation will be rejected because of the correct groupinfo.
> We think when moving, not only groupInfo should be checked, but also relevant
> region assignments should be checked and corrected.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
