[TEZ-3335] DAG client thinks app is still running when app status is null

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.7.1
• Fix Version/s: 0.7.2, 0.9.0, 0.8.5
• Target Version/s: 0.7.2
• Assignee: Jason Darrell Lowe
• Reporter: Jason Darrell Lowe
• Created: 12/Jul/16 16:16
• Updated: 14/Mar/17 03:50
• Resolved: 07/Oct/16 22:16

Description

When an RM restarts without recovering apps (i.e.: either work-preserving is not enabled or state store was removed) and the YARN application history is enabled then YarnClient can return an application report with the app status as null. The RM doesn't know about the application, so the client redirects to the AHS. The AHS knows the app started at some point but will never received a finished event, hence the null app status.

The DAG client fails to detect this scenario and believes the app is still running, so for example Hive clients will continue to hammer for status on an app that doesn't exist.

Issue Links

• relates to: TEZ-3156 Tez client keeps trying to talk to RM even if RM does not know about the application