[
https://issues.apache.org/jira/browse/HADOOP-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-4731:
-------------------------------
Attachment: HADOOP-4731-v1.patch
Attaching patch that fixes the issue. Result of _test-patch_ on my box
{code}
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
{code}
> 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.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.
