hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sameer Paranjpye (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-236) job tracker should refuse connection from a task tracker with a different version number
Date Tue, 30 May 2006 23:37:30 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-236?page=all ]

Sameer Paranjpye updated HADOOP-236:
------------------------------------

    Fix Version: 0.4

> job tracker should refuse connection from a task tracker with a different version number
> ----------------------------------------------------------------------------------------
>
>          Key: HADOOP-236
>          URL: http://issues.apache.org/jira/browse/HADOOP-236
>      Project: Hadoop
>         Type: Bug

>   Components: mapred
>     Versions: 0.2.1
>     Reporter: Hairong Kuang
>      Fix For: 0.4

>
> After one mapred system upgrade, we noticed that all tasks assigned to one task tracker
failed. It turned out that for some reason the task tracker was not upgraded.
> To avoid this, a task tracker should reports its version # when it registers itsself
with a job tracker. If the job tracker receives an inconsistent version #, it should refuse
the connection.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message