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 "Wangda Tan (JIRA)" <ji...@apache.org> on 2015/03/17 22:42:40 UTC
[jira] [Updated] (YARN-3361) CapacityScheduler side changes to
support non-exclusive node labels
[ https://issues.apache.org/jira/browse/YARN-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wangda Tan updated YARN-3361:
-----------------------------
Description:
According to design doc attached in YARN-3214, we need implement following logic in CapacityScheduler:
1) When allocate a resource request with no node-label specified, it should get preferentially allocated to node without labels.
2) When there're some available resource in a node with label, they can be used by applications with following order:
- Applications under queues which can access the label and ask for same labeled resource.
- Applications under queues which can access the label and ask for non-labeled resource.
- Applications under queues cannot access the label and ask for non-labeled resource.
3) Expose necessary information that can be used by preemption policy to make preemption decisions.
was:Reference to design doc attached in YARN-3214, this is CapacityScheduler side changes to support non-exclusive node labels.
> CapacityScheduler side changes to support non-exclusive node labels
> -------------------------------------------------------------------
>
> Key: YARN-3361
> URL: https://issues.apache.org/jira/browse/YARN-3361
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api, client, resourcemanager
> Reporter: Wangda Tan
> Assignee: Wangda Tan
>
> According to design doc attached in YARN-3214, we need implement following logic in CapacityScheduler:
> 1) When allocate a resource request with no node-label specified, it should get preferentially allocated to node without labels.
> 2) When there're some available resource in a node with label, they can be used by applications with following order:
> - Applications under queues which can access the label and ask for same labeled resource.
> - Applications under queues which can access the label and ask for non-labeled resource.
> - Applications under queues cannot access the label and ask for non-labeled resource.
> 3) Expose necessary information that can be used by preemption policy to make preemption decisions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)