[
https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517310#comment-14517310
]
Sunil G commented on YARN-2004:
-------------------------------
Yes [~jlowe] You are correct.
We cannot compare highest priority across queues. If we do not do that, then
there is not much meaning of keeping MAX priority per queue level.
Initially I plan to change that part in another jira where we can have the max
priority application running in queue also to take into consideration while
processing node heartbeat [tries to select which queue can be considered based
on resource consumption]. But this make things more complicated now in CS.
I will be keeping this max in cluster level for now, so it can be accessible
across all queues to make it simple. [~jlowe] [~leftnoteasy] [~vinodkv], pls
share your thoughts.
> Priority scheduling support in Capacity scheduler
> -------------------------------------------------
>
> Key: YARN-2004
> URL: https://issues.apache.org/jira/browse/YARN-2004
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacityscheduler
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: 0001-YARN-2004.patch, 0002-YARN-2004.patch,
> 0003-YARN-2004.patch, 0004-YARN-2004.patch, 0005-YARN-2004.patch,
> 0006-YARN-2004.patch
>
>
> Based on the priority of the application, Capacity Scheduler should be able
> to give preference to application while doing scheduling.
> Comparator<FiCaSchedulerApp> applicationComparator can be changed as below.
>
> 1. Check for Application priority. If priority is available, then return
> the highest priority job.
> 2. Otherwise continue with existing logic such as App ID comparison and
> then TimeStamp comparison.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
