[YARN-7087] NM failed to perform log aggregation due to absent container

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.8.1
• Fix Version/s: 2.9.0, 3.0.0-beta1, 2.8.2
• Component/s: log-aggregation
• Target Version/s: 2.8.2
• Assignee: Jason Darrell Lowe
• Reporter: Jason Darrell Lowe
• Created: 23/Aug/17 20:23
• Updated: 31/Aug/17 21:31
• Resolved: 25/Aug/17 21:07

Description

Saw a case where the NM failed to aggregate the logs for a container because it claimed it was absent:

2017-08-23 18:35:38,283 [AsyncDispatcher event handler] WARN logaggregation.LogAggregationService: Log aggregation cannot be started for container_e07_1503326514161_502342_01_000001, as its an absent container

Containers should not be allowed to disappear if they're not done being fully processed by the NM.

Issue Links

• relates to: YARN-221 NM should provide a way for AM to tell it not to aggregate logs.
• relates to: YARN-4152 NM crash with NPE when LogAggregationService#stopContainer called for absent container