hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-2004) Priority scheduling support in Capacity scheduler
Date Sun, 28 Jun 2015 14:51:06 GMT

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

Sunil G updated YARN-2004:
--------------------------
    Attachment: 0008-YARN-2004.patch

Thank you [~eepayne] for sharing the comments.

bq. Can getApplicationPriority return null?
In CS addApplicationAttempt(), immediately after creating FicaSchedulerApp, I am setting the
priority.
{code}
application.setCurrentAppAttempt(attempt);
attempt.setApplicationPriority(application.getPriority());
{code}

Also from YARN-2003, we set the application priority in all cases while processing submitApplication.
If user didnt set a priority, application will have the default priority from Queue. If user
didnt configure a default priority in Queue, then by default 0(ZERO) will be considered as
default priority.
Please let me know if this is fine.

> 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
>
>
> 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)

Mime
View raw message