[
https://issues.apache.org/jira/browse/HADOOP-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650603#action_12650603
]
Steve Loughran commented on HADOOP-4659:
----------------------------------------
Adding a timeout on TaskTracker's call for waitForProxy() lets us have a
TaskTracker that eventually gives up when the JobTracker isnt there. The other
places that waitForProxy() are called with no timeouts are in the connection
routines of Datanode and SecondaryNameNode(). I think all of these should be
designed to take a configuration parameter that tells them when to give up, and
a default value of many minutes or more to deal with basic choreography issues
in a cluster. Test clusters can be set up to fail sooner rather than later.
Thoughts?
> 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
> Priority: Blocker
> Fix For: 0.18.3
>
> Attachments: connectRetry.patch, hadoop-4659.patch,
> hadoop-4659.patch, rpcConn.patch, rpcConn1.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.
