hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-306) FIFO scheduler doesn't respect changing job priority
Date Wed, 16 Sep 2015 13:46:47 GMT

     [ https://issues.apache.org/jira/browse/YARN-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Lowe resolved YARN-306.
-----------------------------
    Resolution: Won't Fix

bq. Thinking that it may violate FIFO scheduling policy.
Well if we're worried about that then the same logic would apply to the CapacityScheduler.
 It also was using a FIFO scheduling policy before priority support was added.  All that adding
it to the FIFO scheduler would mean is that jobs would be in priority order then FIFO within
the same priority.

However I agree with Jian that we probably don't need to add the support unless there is sufficient
demand.  If users really want the FIFO scheduler with priority then they can run the CapacityScheduler
with a single queue which should be effectively equivalent.

> FIFO scheduler doesn't respect changing job priority
> ----------------------------------------------------
>
>                 Key: YARN-306
>                 URL: https://issues.apache.org/jira/browse/YARN-306
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: scheduler
>    Affects Versions: 2.0.2-alpha
>            Reporter: Nishan Shetty
>            Assignee: Rohith Sharma K S
>
> 1.Submit job
> 2.Change the job priority using setPriority() or CLI command ./mapred job-set-priority
<job-id> <priority>
> Observe that Job priority is not changed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message