[YARN-4771] Some containers can be skipped during log aggregation after NM restart

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.10.0, 3.2.1, 3.1.3
• Fix Version/s: 3.2.2, 3.1.4, 2.10.1, 3.4.0, 3.3.1
• Component/s: nodemanager
• Assignee: Jim Brennan
• Reporter: Jason Darrell Lowe
• Created: 08/Mar/16 14:28
• Updated: 18/Jan/24 15:54
• Resolved: 24/Jul/20 22:36

Description

A container can be skipped during log aggregation after a work-preserving nodemanager restart if the following events occur:

1. Container completes more than yarn.nodemanager.duration-to-track-stopped-containers milliseconds before the restart
2. At least one other container completes after the above container and before the restart