[
https://issues.apache.org/jira/browse/YARN-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Suresh updated YARN-5220:
------------------------------
Fix Version/s: 3.0.0-beta1
> Scheduling of OPPORTUNISTIC containers through YARN RM
> ------------------------------------------------------
>
> Key: YARN-5220
> URL: https://issues.apache.org/jira/browse/YARN-5220
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: resourcemanager
> Reporter: Konstantinos Karanasos
> Assignee: Konstantinos Karanasos
> Priority: Major
> Fix For: 2.9.0, 3.0.0-beta1
>
>
> In YARN-2882, we introduced the notion of OPPORTUNISTIC containers, along
> with the existing GUARANTEED containers of YARN.
> OPPORTUNISTIC containers are allowed to be queued at the NMs (YARN-2883), and
> are executed as long as there are available resources at the NM. Moreover,
> they are of lower priority than the GUARANTEED containers, that is, they can
> be preempted for a GUARANTEED container to start its execution.
> In YARN-2877, we introduced distributed scheduling in YARN, and enabled
> OPPORTUNISTIC containers to be scheduled exclusively by distributed
> schedulers.
> In this JIRA, we are proposing to extend the centralized YARN RM in order to
> enable the scheduling of OPPORTUNISTIC containers in a centralized fashion.
> This way, users can use OPPORTUNISTIC containers to improve the cluster's
> utilization, without the need to enable distributed scheduling.
> This JIRA is also related to YARN-1011 that introduces the over-commitment of
> resources, scheduling additional OPPORTUNISTIC containers to the NMs based on
> the currently used resources and not based only on the allocated resources.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
