[
https://issues.apache.org/jira/browse/HBASE-20682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506289#comment-16506289
]
Josh Elser commented on HBASE-20682:
------------------------------------
bq. We could implement another procedure for reopening a region, but what I
want to say is that, changing the RS side code maybe too much for at least 2.0.
I think I'd defer to your expertise here. If you find that too intrusive, we
could do for later. I think there are ways we can "lessen" this pain (e.g.
HBASE-20706)
bq. The new procedure could still be constructed with an unassign followed by
an assign. What do you folks think?
Seems straightforward enough to me :)
> 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.0.1
>
>
> 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)
