[
https://issues.apache.org/jira/browse/HBASE-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267107#comment-13267107
]
chunhui shen commented on HBASE-5914:
-------------------------------------
@ram
In current process of ServerShutdownHandler, we don't wait until no regions in
transition, and we could keep it.
bq.can we have a configuration like how we have in the master start up to
ensure whether to use roundRobin or not.
When master startup, we use the configuration of
"hbase.master.startup.retainassign" to determine what type of assignment to do
on startup,(retainassign or round-robin fashion), however retainassign is not
appropriate in the process of ServerShutdownHandler since the old server is
already be dead.
> Using bulk assign regions in the process of ServerShutdownHandler
> -----------------------------------------------------------------
>
> Key: HBASE-5914
> URL: https://issues.apache.org/jira/browse/HBASE-5914
> Project: HBase
> Issue Type: Improvement
> Reporter: chunhui shen
> Assignee: chunhui shen
> Attachments: HBASE-5914.patch, HBASE-5914v2.patch
>
>
> In the process of ServerShutdownHandler, we currently assign regions singly.
> In the large cluster, one regionserver always carried many regions, this
> action is quite slow.
> What about using bulk assign regions like cluster start up.
> In current logic, if we failed assigning many regions to one destination
> server, we will wait unitl timeout,
> however in the process of ServerShutdownHandler, we should retry it to
> another server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
