[YARN-1421] Node managers will not receive application finish event where containers ran before RM restart

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Assignee: Omkar Vinit Joshi
• Reporter: Omkar Vinit Joshi
• Created: 18/Nov/13 20:23
• Updated: 11/Jul/14 04:39
• Resolved: 11/Jul/14 04:39

Description

Problem :- Today for every application we track the node managers where containers ran. So when application finishes it notifies all those node managers about application finish event (via node manager heartbeat). However if rm restarts then we forget this past information and those node managers will never get application finish event and will keep reporting finished applications.

Proposed Solution :- Instead of remembering the node managers where containers ran for this particular application it would be better if we depend on node manager heartbeat to take this decision. i.e. when node manager heartbeats saying it is running application (app1, app2) then we should check those application's status in RM's memory

rmContext.getRMApps()

and if either they are not found (very old applications) or they are in their final state (FINISHED, KILLED, FAILED) then we should immediately notify the node manager about the application finish event. By doing this we are reducing the state which we need to store at RM after restart.

Issue Links

• is duplicated by: YARN-1885 RM may not send the app-finished signal after RM restart to some nodes where the application ran before RM restarts
• is related to: YARN-1354 Recover applications upon nodemanager restart