You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Xu Cang (JIRA)" <ji...@apache.org> on 2019/07/16 01:03:00 UTC

[jira] [Commented] (HBASE-22642) Make move operations of RSGroup idempotent

    [ https://issues.apache.org/jira/browse/HBASE-22642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885741#comment-16885741 ] 

Xu Cang commented on HBASE-22642:
---------------------------------

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)