[YARN-8511] When AM releases a container, RM removes allocation tags before it is released by NM

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.0
• Fix Version/s: 3.2.0, 3.1.1
• Component/s: capacity scheduler
• Target Version/s: 3.2.0, 3.1.1
• Hadoop Flags: Reviewed
• Assignee: Weiwei Yang
• Reporter: Weiwei Yang
• Created: 10/Jul/18 08:05
• Updated: 17/Jul/18 02:40
• Resolved: 16/Jul/18 18:19

Description

User leverages PC with allocation tags to avoid port conflicts between apps, we found sometimes they still get port conflicts. This is a similar issue like YARN-4148. Because RM immediately removes allocation tags once AM#allocate asks to release a container, however container on NM has some delay until it actually gets killed and released the port. We should let RM remove allocation tags AFTER NM confirms the containers are released.