[
https://issues.apache.org/jira/browse/HBASE-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268890#comment-13268890
]
Hadoop QA commented on HBASE-5914:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12525380/HBASE-5914v2.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 hadoop23. The patch compiles against the hadoop 0.23.x profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster
org.apache.hadoop.hbase.TestDrainingServer
org.apache.hadoop.hbase.master.TestAssignmentManager
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/1778//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/1778//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/1778//console
This message is automatically generated.
> 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
>
>
> 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
