[YARN-180] Capacity scheduler - containers that get reserved create container token to early

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.23.3
• Fix Version/s: 2.0.3-alpha, 0.23.5
• Component/s: capacityscheduler
• Assignee: Arun Murthy
• Reporter: Thomas Graves
• Created: 22/Oct/12 19:59
• Updated: 03/Sep/14 23:18
• Resolved: 24/Oct/12 14:27

Description

The capacity scheduler has the ability to 'reserve' containers. Unfortunately before it decides that it goes to reserved rather then assigned, the Container object is created which creates a container token that expires in roughly 10 minutes by default.

This means that by the time the NM frees up enough space on that node for the container to move to assigned the container token may have expired.

Issue Links

• relates to: YARN-1417 RM may issue expired container tokens to AM while issuing new containers.