[YARN-1581] Fair Scheduler: containers that get reserved create container token to early

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.2.0
• Component/s: scheduler

Environment

CentOS 6.4

• Assignee: Unassigned
• Reporter: German Florez-Larrahondo
• Created: 09/Jan/14 16:40
• Updated: 09/Jan/14 22:46
• Resolved: 09/Jan/14 22:46

Description

When using the FairScheduler with long running jobs and over-subscribed servers I hit (what I believe is) the same issue reported on https://issues.apache.org/jira/browse/YARN-180 , which talked specifically about the CapacityScheduler:

In my case, with the FairScheduler I am seeing those corner cases when the NodeManager is finally ready to start a container that was reserved but the token was already expired.

Issue Links

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