Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <213055168.1227781305136.JavaMail.jira@brutus>
Date: Thu, 27 Nov 2008 02:21:45 -0800 (PST)
From: "Amar Kamat (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4731) Job is not removed from the waiting
 jobs queue upon completion.
In-Reply-To: <364634815.1227684764176.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Amar Kamat updated HADOOP-4731:
-------------------------------

    Status: Patch Available  (was: Open)

> Job is not removed from the waiting jobs queue upon completion.
> ---------------------------------------------------------------
>
>                 Key: HADOOP-4731
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4731
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/capacity-sched
>    Affects Versions: 0.19.0
>            Reporter: Hemanth Yamijala
>            Assignee: Amar Kamat
>         Attachments: HADOOP-4731-v1.1.patch, HADOOP-4731-v1.patch
>
>
> When a job completes, the {{JobQueueManager}} removes this job from it's internal structures, which is a queue of the running jobs and waiting jobs. While the removal from the running jobs happens correctly, the removal from the waiting jobs does not happen, if the job is still in the PREP state. This was found while implementing HADOOP-4035, as described [by Vinod here|https://issues.apache.org/jira/browse/HADOOP-4035?focusedCommentId=12650879#action_12650879]. The change was introduced in HADOOP-4471, which I should have caught in the review. Sorry about that !

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