hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-65) TaskTrackers never (re)connect back to the JobTracker if the JobTracker node/machine is changed
Date Wed, 30 Jul 2014 17:06:40 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Allen Wittenauer resolved MAPREDUCE-65.
---------------------------------------

    Resolution: Won't Fix

Closing this as Won't Fix.

There are a multitude of ways to get a TT to talk to a new JT, even pre-2.x.  The key is to
not use the machine's IP, but to use  a name that can move (either IP alias or BGP published
or whatever).



> TaskTrackers never (re)connect back to the JobTracker if the JobTracker node/machine
is changed
> -----------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-65
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-65
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message