[
https://issues.apache.org/jira/browse/HBASE-5882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278716#comment-13278716
]
Hadoop QA commented on HBASE-5882:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12528025/hbase_5882_V3.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+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 appears to introduce 32 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.master.TestSplitLogManager
org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/1928//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/1928//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/1928//console
This message is automatically generated.
> Prcoess RIT on master restart can try assigning the region if the region is
> found on a dead server instead of waiting for Timeout Monitor
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-5882
> URL: https://issues.apache.org/jira/browse/HBASE-5882
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.6, 0.92.1
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Attachments: hbase_5882.patch, hbase_5882_V2.patch,
> hbase_5882_V3.patch
>
>
> Currently on master restart if it tries to do processRIT, any region if
> found on dead server tries to avoid the nwe assignment so that timeout
> monitor can take care.
> This case is more prominent if the node is found in RS_ZK_REGION_OPENING
> state. I think we can handle this by triggering a new assignment with a new
> plan.
--
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
