[
https://issues.apache.org/jira/browse/HBASE-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272118#comment-13272118
]
Hudson commented on HBASE-5914:
-------------------------------
Integrated in HBase-TRUNK-security #197 (See
[https://builds.apache.org/job/HBase-TRUNK-security/197/])
HBASE-5914 Bulk assign regions in the process of ServerShutdownHandler
(Chunhui) (Revision 1336308)
Result = FAILURE
tedyu :
Files :
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java
> 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
> Fix For: 0.96.0
>
> Attachments: HBASE-5914.patch, HBASE-5914v2.patch, HBASE-5914v3.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
