[YARN-5074] RM cycles through container ids for an app that is waiting for resources.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.7.2
• Component/s: resourcemanager
• Assignee: Unassigned
• Reporter: Sidharta Seethana
• Created: 11/May/16 21:49
• Updated: 13/May/16 18:07

Description

/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.

Issue Links

• is related to: YARN-5082 Limit ContainerId increase in fair scheduler if the num of node app reserved reached the limit