TaskTrackers never (re)connect back to the JobTracker if the JobTracker
node/machine is changed
-----------------------------------------------------------------------------------------------
Key: HADOOP-4016
URL: https://issues.apache.org/jira/browse/HADOOP-4016
Project: Hadoop Core
Issue Type: Bug
Components: mapred
Reporter: Amar Kamat
I tried the following
1) Started a hadoop cluster.
2) Killed the JT
3) Selected a new node for starting JT.
4) Changed the entry on the tasktracker to reflect the new (old) hostname to
(new) ip mapping. Checked if the tracker node correctly resolves the hostname
to the new ip.
5) Start the JT on the new node
The tasktracker fails to connect to the new jobtracker. It seems that the
hostname resolution remains stale and is never updated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
