You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2010/03/31 22:27:27 UTC

[jira] Updated: (HADOOP-6667) RPC.waitForProxy should retry through NoRouteToHostException

     [ https://issues.apache.org/jira/browse/HADOOP-6667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon updated HADOOP-6667:
--------------------------------

    Attachment: hadoop-6667.txt

Trivial patch attached. There's no test case since this is just like the other existing catch clauses, and any test case would just be testing whether catch clauses indeed work :)

> 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
>            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.