hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-236) job tracker should refuse connection from a task tracker with a different version number
Date Wed, 04 Jun 2008 18:20:45 GMT

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

Owen O'Malley updated HADOOP-236:
---------------------------------

    Status: Open  (was: Patch Available)

The revision isn't strong enough, if you make a change and restart the cluster, an old task
tracker would still agree. It really should be:

{code}
VersionInfo.getVersion() + " from " + VersionInfo.getRevision() + " by " + 
VersionInfo.getUser() + " on " + VersionInfo.getDate()
{code}

> 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: Sharad Agarwal
>             Fix For: 0.18.0
>
>         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.


Mime
View raw message