You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2008/10/01 15:29:49 UTC
[jira] Commented: (HADOOP-4274) Capacity scheduler's implementation
of getJobs modifies the list of running jobs inadvertently
[ https://issues.apache.org/jira/browse/HADOOP-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636031#action_12636031 ]
Hudson commented on HADOOP-4274:
--------------------------------
Integrated in Hadoop-trunk #620 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/620/])
. Capacity scheduler accidently modifies the underlying
data structures when browing the job lists. (Hemanth Yamijala via omalley)
> Capacity scheduler's implementation of getJobs modifies the list of running jobs inadvertently
> ----------------------------------------------------------------------------------------------
>
> Key: HADOOP-4274
> URL: https://issues.apache.org/jira/browse/HADOOP-4274
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: HADOOP-4274.patch
>
>
> The implementation of the {{getJobs}} API gets the running jobs queue from the {{JobQueueManager}}. If it is not null, it appends waiting jobs to the list and returns that. This modifies the original list of running jobs and can affect the scheduler drastically.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.