[YARN-1417] RM may issue expired container tokens to AM while issuing new containers.

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.4.0
• Hadoop Flags: Reviewed
• Assignee: Jian He
• Reporter: Omkar Vinit Joshi
• Created: 15/Nov/13 22:24
• Updated: 10/Apr/14 13:11
• Resolved: 13/Feb/14 22:02

Description

Today we create new container token when we create container in RM as a part of schedule cycle. However that container may get reserved or assigned. If the container gets reserved and remains like that (in reserved state) for more than container token expiry interval then RM will end up issuing container with expired token.

Issue Links

• duplicates: YARN-1581 Fair Scheduler: containers that get reserved create container token to early
• is blocked by: YARN-713 ResourceManager can exit unexpectedly if DNS is unavailable
• is related to: YARN-180 Capacity scheduler - containers that get reserved create container token to early