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 "Yoram Arnon (JIRA)" <ji...@apache.org> on 2006/05/17 19:52:05 UTC

[jira] Created: (HADOOP-225) tasks are left over when a job fails

tasks are left over when a job fails
------------------------------------

         Key: HADOOP-225
         URL: http://issues.apache.org/jira/browse/HADOOP-225
     Project: Hadoop
        Type: Bug

  Components: mapred  
    Reporter: Yoram Arnon
    Priority: Minor


when jobs are stopped or otherwise fail, tasks are often left around.
the job tracker shows that there are map or reduce (mostly reduce) tasks running, when no job is running.
these accumulate over time.
eventually there are so many of those, that the job tracker can't launch new tasks, requiring a restart of the MR cluster.

-- 
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-225) tasks are left over when a job fails

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

Sameer Paranjpye updated HADOOP-225:
------------------------------------

    Fix Version: 0.4
        Version: 0.2

> tasks are left over when a job fails
> ------------------------------------
>
>          Key: HADOOP-225
>          URL: http://issues.apache.org/jira/browse/HADOOP-225
>      Project: Hadoop
>         Type: Bug

>   Components: mapred
>     Versions: 0.2
>     Reporter: Yoram Arnon
>     Priority: Minor
>      Fix For: 0.4

>
> when jobs are stopped or otherwise fail, tasks are often left around.
> the job tracker shows that there are map or reduce (mostly reduce) tasks running, when no job is running.
> these accumulate over time.
> eventually there are so many of those, that the job tracker can't launch new tasks, requiring a restart of the MR cluster.

-- 
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] Resolved: (HADOOP-225) tasks are left over when a job fails

Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Owen O'Malley resolved HADOOP-225.
----------------------------------

    Resolution: Cannot Reproduce

We haven't seen this in a long time.

> tasks are left over when a job fails
> ------------------------------------
>
>                 Key: HADOOP-225
>                 URL: https://issues.apache.org/jira/browse/HADOOP-225
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.2.0
>            Reporter: Yoram Arnon
>         Assigned To: Owen O'Malley
>            Priority: Minor
>
> when jobs are stopped or otherwise fail, tasks are often left around.
> the job tracker shows that there are map or reduce (mostly reduce) tasks running, when no job is running.
> these accumulate over time.
> eventually there are so many of those, that the job tracker can't launch new tasks, requiring a restart of the MR cluster.

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


[jira] Commented: (HADOOP-225) tasks are left over when a job fails

Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/HADOOP-225?page=comments#action_12446061 ] 
            
Owen O'Malley commented on HADOOP-225:
--------------------------------------

Has anyone seen this recently or can we close it?

> tasks are left over when a job fails
> ------------------------------------
>
>                 Key: HADOOP-225
>                 URL: http://issues.apache.org/jira/browse/HADOOP-225
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.2.0
>            Reporter: Yoram Arnon
>            Priority: Minor
>
> when jobs are stopped or otherwise fail, tasks are often left around.
> the job tracker shows that there are map or reduce (mostly reduce) tasks running, when no job is running.
> these accumulate over time.
> eventually there are so many of those, that the job tracker can't launch new tasks, requiring a restart of the MR cluster.

-- 
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] Commented: (HADOOP-225) tasks are left over when a job fails

Posted by "Yoram Arnon (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/HADOOP-225?page=comments#action_12446067 ] 
            
Yoram Arnon commented on HADOOP-225:
------------------------------------

Not sure:
- I haven't been monitoring this as much lately.
- JT crashes too frequently to get a decent statistic

Let's check in a few days

Yoram 



> tasks are left over when a job fails
> ------------------------------------
>
>                 Key: HADOOP-225
>                 URL: http://issues.apache.org/jira/browse/HADOOP-225
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.2.0
>            Reporter: Yoram Arnon
>            Priority: Minor
>
> when jobs are stopped or otherwise fail, tasks are often left around.
> the job tracker shows that there are map or reduce (mostly reduce) tasks running, when no job is running.
> these accumulate over time.
> eventually there are so many of those, that the job tracker can't launch new tasks, requiring a restart of the MR cluster.

-- 
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-225) tasks are left over when a job fails

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

Doug Cutting updated HADOOP-225:
--------------------------------

    Fix Version: 0.5.0
                     (was: 0.4.0)

> tasks are left over when a job fails
> ------------------------------------
>
>          Key: HADOOP-225
>          URL: http://issues.apache.org/jira/browse/HADOOP-225
>      Project: Hadoop
>         Type: Bug

>   Components: mapred
>     Versions: 0.2.0
>     Reporter: Yoram Arnon
>     Priority: Minor
>      Fix For: 0.5.0

>
> when jobs are stopped or otherwise fail, tasks are often left around.
> the job tracker shows that there are map or reduce (mostly reduce) tasks running, when no job is running.
> these accumulate over time.
> eventually there are so many of those, that the job tracker can't launch new tasks, requiring a restart of the MR cluster.

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