Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Message-ID: <1904938242.1248936974806.JavaMail.jira@brutus>
Date: Wed, 29 Jul 2009 23:56:14 -0700 (PDT)
From: "Nathan Marz (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Subject: [jira] Resolved: (HADOOP-5330) Zombie tasks remain after jobs
 finish/fail/get killed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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