[YARN-8980] Mapreduce application container start fail after AM restart.

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.4.0
• Component/s: federation
• Labels: pull-request-available
• Target Version/s: 3.4.0
• Hadoop Flags: Reviewed
• Assignee: Chenyu Zheng
• Reporter: Bibin Chundatt
• Created: 06/Nov/18 18:44
• Updated: 12/Feb/24 06:50
• Resolved: 09/Sep/23 01:52

Description

UAM to subclusters are always launched with keepContainers.

On AM restart scenarios , UAM register again with RM . UAM receive running containers with NMToken. NMToken received by UAM in getPreviousAttemptContainersNMToken is never used by mapreduce application.

Federation Interceptor should take care of such scenarios too. Merge NMToken received at registration to allocate response.

Container allocation response on same node will have NMToken empty.

issue credits : Nallasivan

Issue Links

• links to: GitHub Pull Request #5975