Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
0.14.0
-
None
-
None
Description
The exception is similar to HADOOP-1739 but it seems to be a different reason for us. We have a multi homed boxes and have specified the mapred.task.tracker.report.bindAddress to be a local 192.x address. The tracker process only uses the default constructor to create an InetSocketAddress in TaskTracker and misses to connect to the report server which is listening on 192.x now.
The attached patch should solve that.