[YARN-4946] RM should not consider an application as COMPLETED when log aggregation is not in a terminal state

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.0
• Fix Version/s: 3.2.0
• Component/s: log-aggregation
• Target Version/s: 3.2.0
• Hadoop Flags: Reviewed
• Assignee: Szilard Nemeth
• Reporter: Robert Kanter
• Created: 12/Apr/16 02:06
• Updated: 15/Oct/20 16:09
• Resolved: 09/Aug/18 22:20

Description

MAPREDUCE-6415 added a tool that combines the aggregated log files for each Yarn App into a HAR file. When run, it seeds the list by looking at the aggregated logs directory, and then filters out ineligible apps. One of the criteria involves checking with the RM that an Application's log aggregation status is not still running and has not failed. When the RM "forgets" about an older completed Application (e.g. RM failover, enough time has passed, etc), the tool won't find the Application in the RM and will just assume that its log aggregation succeeded, even if it actually failed or is still running.

We can solve this problem by doing the following:
The RM should not consider an app to be fully completed (and thus removed from its history) until the aggregation status has reached a terminal state (e.g. SUCCEEDED, FAILED, TIME_OUT).

Issue Links

• is related to: YARN-9848 revert YARN-4946
• is related to: MAPREDUCE-6415 Create a tool to combine aggregated logs into HAR files
• is related to: YARN-9571 RM state store purging should be configurable if log aggregation does not terminate