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 "Hairong Kuang (JIRA)" <ji...@apache.org> on 2006/05/19 21:18:29 UTC

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

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


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

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

Posted by Eric Baldeschwieler <er...@yahoo-inc.com>.
And log / report the problem of course!

On May 19, 2006, at 12:18 PM, Hairong Kuang (JIRA) wrote:

> 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
>
>
> 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
>

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

Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
     [ 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

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

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-236?page=all ]

Doug Cutting updated HADOOP-236:
--------------------------------

    Fix Version: 0.5.0
                     (was: 0.4.0)

> 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.5.0

>
> 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