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

Posted to issues@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2019/02/13 02:48:00 UTC

[jira] [Updated] (HBASE-20682) MoveProcedure can be subtask of ModifyTableProcedure/ReopenTableRegionsProcedure; ensure all kosher.

     [ https://issues.apache.org/jira/browse/HBASE-20682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guanghao Zhang updated HBASE-20682:
-----------------------------------
    Fix Version/s:     (was: 2.2.0)
                   2.3.0

> MoveProcedure can be subtask of ModifyTableProcedure/ReopenTableRegionsProcedure; ensure all kosher.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-20682
>                 URL: https://issues.apache.org/jira/browse/HBASE-20682
>             Project: HBase
>          Issue Type: Sub-task
>          Components: amv2
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.3.0
>
>
> MoveProcedure is used in at least two places as a means of 'reopening' a region after a config has changed. This issue is about review of MP so this usage is first-class (and that MP is good procedure citizen running as a subprocedure. In question is what should happen if the source server or the target servers are offline when we go to run. As of the parent issue, we'll skip to the end. Should we instead go ahead with the move (internally, if we are asked to assign to an offline server, we'll pick another -- do same for unassign? Would help in this reopen use case).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)