[jira] [Commented] (YARN-2004) Priority scheduling support in Capacity scheduler

["Jian He (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611034#comment-14611034 ] 

Jian He commented on YARN-2004:
-------------------------------

- authenticateApplicationPriority : IIUC, all it does is just to take the config from yarn-site.xml (not capacity-scheduler.xml) and check the priority against that. I don't see much need of explicitly exposing an API in scheduler and inject the check there. Or this method has more responsibility than that ?

- Given that  YARN-2003 is just the API of YARN-2004 and we anyways have to review the two altogether,  we may merge the two into a single patch ? This is easier for review and you also do not need to split the patch and upload in two different places. And you can actually split the part about updating application priority at runtime and state store changes into a different patch.

> 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, 0007-YARN-2004.patch, 0008-YARN-2004.patch, 0009-YARN-2004.patch, 0010-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)