[
https://issues.apache.org/jira/browse/HADOOP-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651760#action_12651760
]
Hadoop QA commented on HADOOP-4731:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12394834/HADOOP-4731-v1.1.patch
against trunk revision 721415.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3672/console
This message is automatically generated.
> 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.
