You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sunil G (JIRA)" <ji...@apache.org> on 2015/06/25 17:18:04 UTC
[jira] [Updated] (YARN-2004) Priority scheduling support in
Capacity scheduler
[ https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunil G updated YARN-2004:
--------------------------
Attachment: 0007-YARN-2004.patch
Rebasing patch against latest trunk. Also made changes as per OrderingPolicy in CS.
> 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
>
>
> 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)