Affects Version/s: 0.21.0
Fix Version/s: None
It's OK for your job tracker's config to tells the JobTracker to come up on port 0:0:0:0, but its not OK for the TaskTrackers to get the same mapred.job.tracker configuration value, as it stops the TT from being able to report its heartbeat.
This misconfiguration surfaces in the TT's offerService() routine catching and logging a ConnectionRefused exception every time it tries to heartbeat. Now we have improved the error message in such a situation, it is still a bit late in the process to encounter a problem which should be obvious the moment the TT looks at its configuration.
Better to have the TT refuse to start up if jobTrackAddr.getAddress().isAnyLocalAddress().
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Incomplete [ 4 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1780d 8h||1||Allen Wittenauer||24/Jul/14 00:06|