[HADOOP-4659] Root cause of connection failure is being lost to code that uses it for delaying startup - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Blocker
Resolution: Fixed
Affects Version/s: 0.18.3
Fix Version/s: 0.18.3
Component/s: ipc
Labels:
None

Hadoop Flags:

Incompatible change, Reviewed

Description

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.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

hadoop-4659.patch
14/Nov/08 16:14
1 kB
Steve Loughran
connectRetry.patch
17/Nov/08 19:32
0.7 kB
Hairong Kuang
rpcConn.patch
19/Nov/08 01:07
3 kB
Hairong Kuang
hadoop-4659.patch
19/Nov/08 17:21
6 kB
Steve Loughran
rpcConn1.patch
24/Nov/08 19:43
6 kB
Hairong Kuang

Issue Links

is blocked by

HADOOP-4703 DataNode.createInterDataNodeProtocolProxy should not wait for proxy forever while recovering lease

Closed

is depended upon by

HADOOP-4724 TaskTracker, DataNode, and SecondaryNameNode should timeout on waiting for its server to be up

Open

Activity

People

Assignee:: Steve Loughran

Reporter:: Steve Loughran

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 14/Nov/08 14:49

Updated:: 02/May/13 02:29

Resolved:: 25/Nov/08 21:45