You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Sharad Agarwal (JIRA)" <ji...@apache.org> on 2008/05/29 12:18:45 UTC

[jira] Updated: (HADOOP-236) job tracker should refuse connection from a task tracker with a different version number

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

Sharad Agarwal updated HADOOP-236:
----------------------------------

    Attachment: 236_v1.patch

On relook, seems like buildVersion check at the initialContact is sufficient  (similar to the Namenode/Datanode model).
Attaching the patch for review.

> job tracker should refuse connection from a task tracker with a different version number
> ----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-236
>                 URL: https://issues.apache.org/jira/browse/HADOOP-236
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.2.1
>            Reporter: Hairong Kuang
>            Assignee: Owen O'Malley
>         Attachments: 236_v1.patch
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.