[
https://issues.apache.org/jira/browse/HBASE-20682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505401#comment-16505401
]
stack commented on HBASE-20682:
-------------------------------
bq.
With the new remote procedure framework we can just introduce a new remote
procedure callable and use executeProcedure to run it, so we do not need to add
a new method. And yeah we do not have this framework in 2.0...
That sounds sweet.
Another thought was adding a flag to CloseRegionRequest. The flag would be
reopen. If present, the RS would close and then reopen the Region and return in
CloseRegionRequest that it had done the reopen. If the RS did not support this
functionality, the Procedure running the 'reopen' would follow the close by an
open request.
bq. But if there is a MRP which is moving the meta region, then the region is
offline check will return false and we will stuck there forever...
Is this HBASE-20700?
Good find.
> 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)
