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 2016/05/11 23:54:13 UTC
[jira] [Updated] (YARN-5074) RM cycles through container ids for an
app that is waiting for resources.
[ https://issues.apache.org/jira/browse/YARN-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wangda Tan updated YARN-5074:
-----------------------------
Attachment: YARN-5074-test-case.patch
> RM cycles through container ids for an app that is waiting for resources.
> --------------------------------------------------------------------------
>
> Key: YARN-5074
> URL: https://issues.apache.org/jira/browse/YARN-5074
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.7.2
> Reporter: Sidharta Seethana
> Attachments: YARN-5074-test-case.patch
>
>
> /cc [~wangda], [~vinodkv]
> This was observed on a cluster running a 2.7.x build. Here is the scenario :
> 1. A YARN cluster has applications running that almost entirely consume the cluster, with little available resources.
> 2. A new app is submitted - the resources required for the AM exceed what is available in the cluster. The app stays in the 'ACCEPTED' state till resources are available.
> 3. Once resources are available and the AM container comes up, the AM container has a id that indicates that the RM has been cycling through containers. There are no errors in the logs of any kind. One example id for such an AM container is : container_e3788_1462916288781_0012_01_000302 . This indicates that while the app was in the 'ACCEPTED' state, the RM cycled through 301 containers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org