hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4659) Root cause of connection failure is being lost to code that uses it for delaying startup
Date Mon, 17 Nov 2008 17:15:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648193#action_12648193
] 

Raghu Angadi commented on HADOOP-4659:
--------------------------------------

> Client.call doesnt catch the exception. ...

right. call() and waitForProxy() didn't change w.r.t. this. Now I see : the main difference
is that setupIOstreams() used to throw the exception it got before HADOOP-2188. I think it
should still throw. The local exception was supposed to be rare (some other connection error
after writing the initial RPC request). Throwing the exception in setupIOStreams() will get
this behavior to match pre-HADOOP-2188.

I think this should be a blocker for 0.18.3.


> Root cause of connection failure is being lost to code that uses it for delaying startup
> ----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4659
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4659
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.18.3
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>             Fix For: 0.18.3
>
>         Attachments: hadoop-4659.patch
>
>
> ipc.Client the root cause of a connection failure is being lost as the exception is wrapped,
hence the outside code, the one that looks for that root cause, isn't working as expected.
The results is you can't bring up a task tracker before job tracker, and probably the same
for a datanode before a  namenode. The change that triggered this is not yet located, I had
thought it was HADOOP-3844 but I no longer believe this is the case.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message