[
https://issues.apache.org/jira/browse/HADOOP-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640163#action_12640163
]
Karam Singh commented on HADOOP-4428:
-------------------------------------
TestCase-1:
Submitted 6 jobs at same time with different users as follows -:
User1 Job1 maps=reduces=212 priority=VERY_LOW
User2 Job2 maps=reduces=212 priority=LOW
User3 Job3 maps=reduces=212 priority=HIGH
User4 Job4 maps=reduces=212 priority=VERY_HIGH
User5 Job5 maps=reduces=212 priority=VERY_LOW
User6 Job6 maps=reduces=212 priority=VERY_HIGH
The JobTracker UI shows all 6 jobs as running with -:
J1, maps=reduces=53 running, Priority =VERY_LOW
J2, maps=reduces=0 running, Priority=LOW
J3, maps=, reduces=53 running, Priority=HIGH
J4, maps=reduces=0 running, Priority=VERY_HIGH
J5, maps=reduces=53, Priority=VERY_LOW
J6, maps=reduces=53, Priority=VERY_HIGH
Where expected behavior should like -:
Maps and reduces of J2, J3, J4, J6 start running while maps and reduces J1, J5
remain in queue.
TestCase-2:
First submitted J1, User7 maps=reduces=212 priority=NORMAL. (SleepJob with
-rt=1)
When J1 started running, submitted 6 jobs at same time with different users -:
User1 Job2 maps=reduces=212 priority=VERY_LOW
User2 Job3 maps=reduces=212 priority=LOW
User3 Job4 maps=reduces=212 priority=HIGH
User4 Job5 maps=reduces=212 priority=VERY_HIGH
User5 Job6 maps=reduces=212 priority=VERY_LOW
User6 Job7 maps=reduces=212 priority=VERY_HIGH
"hadoop job -list" shows state of J2-J7 =4. When maps of J1 started finishing
J2-J7 started running. The JobTracker UI shows status after J1 finishes as -:
J2, maps=reduces=53 running, Priority =VERY_LOW
J3, maps=reduces=53 running, Priority=LOW
J4, maps=, reduces=0 running, Priority=HIGH
J5, maps=reduces=53 running, Priority=VERY_HIGH
J6, maps=reduces=53, Priority=VERY_LOW
J7, maps=reduces=0, Priority=VERY_HIGH
Where Expected behavior should be -:
Maps and reduces of J3, J4, J5, J7 start running while maps and reduces J2, J6
remain in queue.
Note -: Preivously it was working as expected
> 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
>
> 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.
