[
https://issues.apache.org/jira/browse/HBASE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257687#comment-13257687
]
Hadoop QA commented on HBASE-5809:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12523374/HBASE-5809.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 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 6 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:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/1578//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/1578//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/1578//console
This message is automatically generated.
> Avoid move api to take the destination server same as the source server.
> ------------------------------------------------------------------------
>
> Key: HBASE-5809
> URL: https://issues.apache.org/jira/browse/HBASE-5809
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.1
> Reporter: ramkrishna.s.vasudevan
> Priority: Minor
> Labels: patch
> Fix For: 0.96.0, 0.94.1
>
> Attachments: HBASE-5809.patch
>
>
> In Move currently we take any destination specified and if the destination is
> same as the source we still do unassign and assign. Here we can have
> problems due to RegionAlreadyInTransitionException and thus hanging the
> region in RIT for long time. We can avoid this scenario by not allowing the
> move to happen in this scenario.
--
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
