[
https://issues.apache.org/jira/browse/HBASE-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449518#comment-13449518
]
Hadoop QA commented on HBASE-6713:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12543997/HBASE-6713v2.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 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
-1 javadoc. The javadoc tool appears to have generated 108 warning
messages.
-1 javac. The applied patch generated 5 javac compiler warnings (more than
the trunk's current 4 warnings).
-1 findbugs. The patch appears to introduce 7 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.backup.example.TestZooKeeperTableArchiveClient
org.apache.hadoop.hbase.catalog.TestMetaReaderEditor
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2800//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2800//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2800//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2800//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2800//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2800//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2800//console
This message is automatically generated.
> Stopping meta/root RS may take 50mins when it is in region-splitting
> --------------------------------------------------------------------
>
> Key: HBASE-6713
> URL: https://issues.apache.org/jira/browse/HBASE-6713
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.94.1
> Reporter: chunhui shen
> Assignee: chunhui shen
> Fix For: 0.96.0, 0.94.3
>
> Attachments: HBASE-6713.patch, HBASE-6713v2.patch
>
>
> When we stop the RS carrying ROOT/META, if it is in the splitting for some
> region, the whole stopping process may take 50 mins.
> The reason is :
> 1.ROOT/META region is closed when stopping the regionserver
> 2.The Split Transaction failed updating META and it will retry
> 3.The retry num is 100, and the total time is about 50 mins as default;
> This configuration is set by
> HConnectionManager#setServerSideHConnectionRetries
> I think 50 mins is too long to acceptable, my suggested solution is closing
> MetaTable regions after the compact/split thread is closed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
