[
https://issues.apache.org/jira/browse/HBASE-22642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921095#comment-16921095
]
Hudson commented on HBASE-22642:
--------------------------------
Results for branch master
[build #1391 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1391/]: (x)
*{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1368//General_Nightly_Build_Report/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
> Fix For: 3.0.0, 2.3.0
>
>
> 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
(v8.3.2#803003)
