hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Marz (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-5330) Zombie tasks remain after jobs finish/fail/get killed
Date Thu, 30 Jul 2009 06:56:14 GMT

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

Nathan Marz resolved HADOOP-5330.
---------------------------------

    Resolution: Invalid

As it turns out, this was caused by an application problem. We were running embedded Solr
instances in the tasks that were preventing the process from exiting. The fix was to close
the Solr instances at task completion.

> Zombie tasks remain after jobs finish/fail/get killed
> -----------------------------------------------------
>
>                 Key: HADOOP-5330
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5330
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.19.1
>            Reporter: Nathan Marz
>
> I'm seeing a lot of "task attempts" around our hadoop cluster for jobs that are no longer
around. The attempts seem to be "hung", as they sit there forever. Additionally, they seem
to take up map and reduce slots in the cluster unless MapReduce is restarted. This causes
real jobs to be unable to utilize the whole cluster.

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