Rohith Sharma K S commented on YARN-306:

Agree for on-demand implementing priority support in FIFO scheduler. And work 
around also exist with CS.
Sorry I did not give my full thoughts on violating FIFO scheduling policy what 
it by means. In CS, choosing of queues at the same level is based on the sorted 
order of child Queues by used-capacity. If used capacity is same across the 
queues then sorted using guaranteed capacity. At leafQueue level, FIFO policy 
is used which is changed now with priority as first. Basically CS tries to 
choose the queue's at same level by capacity but in FIFO scheduler there is no 
queue concept, applications are assigned in FIFO order. In CS, fifo policy at 
leaf queue is violated which is one part of CS, where as FIFO scheduler will be 
violating fully if priority supports.

> 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

Reply via email to