[
https://issues.apache.org/jira/browse/HADOOP-6667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852097#action_12852097
]
Hadoop QA commented on HADOOP-6667:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12440401/hadoop-6667.txt
against trunk revision 927979.
+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 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 warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/435/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/435/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/435/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/435/console
This message is automatically generated.
> RPC.waitForProxy should retry through NoRouteToHostException
> ------------------------------------------------------------
>
> Key: HADOOP-6667
> URL: https://issues.apache.org/jira/browse/HADOOP-6667
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Attachments: hadoop-6667.txt
>
>
> RPC.waitForProxy already loops through ConnectExceptions, but
> NoRouteToHostException is not a subclass of ConnectException. In the case
> that the NN is on a VIP, the No Route To Host error is reasonably common
> during a failover, so we should retry through it just the same as the other
> connection errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
