hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6667) RPC.waitForProxy should retry through NoRouteToHostException
Date Wed, 31 Mar 2010 20:27:27 GMT

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

View raw message