[
https://issues.apache.org/jira/browse/YARN-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302033#comment-16302033
]
Subru Krishnan commented on YARN-1051:
--------------------------------------
[~xingbao], the behavior depends on whether there's any job that's using more
than it's guaranteed resources in the specific node and if preemption is
enabled or not in the cluster.
If there's no job using excess resources in the specific node, then either:
* relax locality to rack
* wait for one of the running job AMs to release container(s)
If there is at least one job which is using excess resources in the specific
node, then:
* If you have preemption is enabled (refer
[http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html#Capacity_Scheduler_container_preemption|here]
on how to enable it), the over allocated container(s) will get preempted
* wait for one of the running job AMs to release container(s)
> YARN Admission Control/Planner: enhancing the resource allocation model with
> time.
> ----------------------------------------------------------------------------------
>
> Key: YARN-1051
> URL: https://issues.apache.org/jira/browse/YARN-1051
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler, resourcemanager, scheduler
> Reporter: Carlo Curino
> Assignee: Carlo Curino
> Fix For: 2.6.0
>
> Attachments: YARN-1051-design.pdf, YARN-1051.1.patch,
> YARN-1051.patch, curino_MSR-TR-2013-108.pdf, socc14-paper15.pdf,
> techreport.pdf
>
>
> In this umbrella JIRA we propose to extend the YARN RM to handle time
> explicitly, allowing users to "reserve" capacity over time. This is an
> important step towards SLAs, long-running services, workflows, and helps for
> gang scheduling.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
