[
https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397293#comment-13397293
]
Hadoop QA commented on HBASE-6227:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12532648/HBASE-6227v2.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 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 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 passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2197//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2197//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2197//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2197//console
This message is automatically generated.
> SSH and cluster startup causes data loss
> -----------------------------------------
>
> Key: HBASE-6227
> URL: https://issues.apache.org/jira/browse/HBASE-6227
> Project: HBase
> Issue Type: Bug
> Components: master
> Reporter: chunhui shen
> Assignee: chunhui shen
> Attachments: HBASE-6227.patch, HBASE-6227v2.patch
>
>
> In AssignmentManager#processDeadServersAndRegionsInTransition, if
> servershutdownhandler is processing and master consider it cluster startup,
> master will assign all user regions, however, servershutdownhandler has not
> completed splitting logs.
> Let me describe it in more detail.
> Suppose there are two regionservers A1 and B1, A1 carried META and ROOT
> 1.master restart and completed assignRootAndMeta
> 2.A1 and B1 are both restarted, new regionservers are A2 and B2
> 3.SSH which processed for A1 completed assigning ROOT and META
> 4.master do rebuilding user regions and no regions added to master's region
> list
> 5.master consider it as a cluster startup, and assign all user regions
> 6.SSH which processed for B1 start to split B1's logs
> 7.All regions' data carried by B1 would loss.
--
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
