hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4428) Job Priorities are not handled properly
Date Thu, 16 Oct 2008 14:31:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640181#action_12640181
] 

Vinod K V commented on HADOOP-4428:
-----------------------------------

Don't know for sure if this is the right fix, but one way of solving this is by maintaining
a sorted order of running-jobs queue, just like waiting job's queue. Then, irrespective of
the order in which set-up tasks get launched and return, running jobs would be served in the
order of priority.

One effect of the above fix is that, a higher priority job that is submitted after a lower
priority job starts running, though will not preempt tasks of lower priority job, will be
given more importance once there are free slots or once tasks of lower priority job started
finishing.

> 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.


Mime
View raw message