[YARN-433] When RM is catching up with node updates then it should not expire acquired containers

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: resourcemanager
• Hadoop Flags: Reviewed
• Assignee: Xuan Gong
• Reporter: Bikas Saha
• Created: 27/Feb/13 23:05
• Updated: 30/Aug/16 01:32
• Resolved: 31/Jul/15 05:10

Description

RM expires containers that are not launched within some time of being allocated. The default is 10mins. When an RM is not keeping up with node updates then it may not be aware of new launched containers. If the expire thread fires for such containers then the RM can expire them even though they may have launched.