[
https://issues.apache.org/jira/browse/HADOOP-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640927#action_12640927
]
Amar Kamat commented on HADOOP-4428:
------------------------------------
Few comments :
1) The other {{submitJob}} api in {{TestCapacityScheduler}} should call the new
{{submitJob}} api with {{NORMAL}} priority.
2) {{testJobPriorities()}} : What is the need to running a large job that takes
up the cluster? Wouldn't a tasktracker with just one slot suffice? Something
like this
{code}
1) submit 5 jobs with different priorities
2) check if they are sorted as expected
3) init the first job in the waiting queue.
4) check assignTasks() to see if no task is assigned.
5) launch setup tasks for the first job in the waiting queue
6) check assignTasks() to see if the result is as expected
7) finish the just launched task to free up the slot
8) do (5), (6) and (7) for other jobs in the waiting queue.
{code}
Rest of the code looks fine.
> 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: Vinod K V
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: HADOOP-4428-20081017.1.txt
>
>
> 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.
