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 "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2015/09/08 04:49:45 UTC
[jira] [Updated] (YARN-4125) In addition to aggregate availability
for an app, headroom should provide information on largest container that
can be allcoated
[ https://issues.apache.org/jira/browse/YARN-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karthik Kambatla updated YARN-4125:
-----------------------------------
Description:
Today, headroom is an indicator to an application on the resources available to it. It is an aggregate across all nodes. If all the nodes have either only memory or only cpu available, no container can be allocated. The headroom should hint at this too, so apps can make decisions sooner. MAPREDUCE-6470 is a case of this, and has an example for the curious.
May be, we should add an API that returns both aggregate headroom and large container allocatable.
was:
Today, headroom is an indicator to an application on the resources available to it. It is an aggregate across all nodes. If all the nodes have either only memory or only cpu available, no container can be allocated. The headroom should hint at this too, so apps can make decisions sooner.
May be, we should add an API that returns both aggregate headroom and large container allocatable.
> In addition to aggregate availability for an app, headroom should provide information on largest container that can be allcoated
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-4125
> URL: https://issues.apache.org/jira/browse/YARN-4125
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: scheduler
> Affects Versions: 2.7.1
> Reporter: Karthik Kambatla
>
> Today, headroom is an indicator to an application on the resources available to it. It is an aggregate across all nodes. If all the nodes have either only memory or only cpu available, no container can be allocated. The headroom should hint at this too, so apps can make decisions sooner. MAPREDUCE-6470 is a case of this, and has an example for the curious.
> May be, we should add an API that returns both aggregate headroom and large container allocatable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)