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] Resolved: (HADOOP-5203) TT's version build is too restrictive
Date Tue, 10 Feb 2009 07:36:59 GMT

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

Owen O'Malley resolved HADOOP-5203.

    Resolution: Won't Fix

This is a feature. One common failure mode is that some nodes fail to get the update of a
new jar file. Without this feature, they attempt to join the cluster and can create serious
problems. Currently, both map/reduce and hdfs require that masters and slaves are from the
same build, which is a very good thing.

> TT's version build is too restrictive
> -------------------------------------
>                 Key: HADOOP-5203
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5203
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: Runping Qi
> At start time, TT checks whether its version is compatible with JT.
> The condition is too restrictive. 
> It will shut down itself if one of the following conditions fail:
> * the version numbers must match
> * the revision numbers must match
> * the user ids who build the jar must match
> * the build times must match
> I think it should check the major part of the version numbers only (thus any version
like 0.19.xxxx should be compatible).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message