[
https://issues.apache.org/jira/browse/HADOOP-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated HADOOP-4428:
-------------------------------------
Resolution: Duplicate
Status: Resolved (was: Patch Available)
As per discussions that have happened on this issue, there are two separate
issues identified:
- Tasks get initialized without a limit on the count initialized at a given
point.
- Jobs are run out of priority order.
HADOOP-4513 moves task initialization in the capacity scheduler to a separate
thread. As part of that issue, we are working on limits to control the count.
HADOOP-4471 sorts jobs in the running queue as well. Hence, jobs are now sorted
in priority order everywhere.
In other words, the two identified issues are resolved if both the above JIRAs
are fixed. Hence, I am closing this issue as a duplicate.
> Job Priorities are not handled properly
> ----------------------------------------
>
> Key: HADOOP-4428
> URL: https://issues.apache.org/jira/browse/HADOOP-4428
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Affects Versions: 0.19.0
> Environment: Cluster: 106 TTs MapCapacity=212, ReduceCapacity=212
> Single Queue=default, User Limit=25, Priorities = Yes.
> Using hadoop branch 0.19 revision=705159
> Reporter: Karam Singh
> Assignee: Sreekanth Ramakrishnan
> Priority: Blocker
> Fix For: 0.19.1
>
> Attachments: HADOOP-4428-20081017.1.txt, HADOOP-4428-20081020.txt,
> HADOOP-4428.patch
>
>
> Job Priorities are not handled properly
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
