[LIVY-865] Livy identify valid yarn state of batch session as FAIL unexpectedly

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.7.0
• Fix Version/s: 0.9.0
• Component/s: Server
• Assignee: Unassigned
• Reporter: Du Ripeng
• Created: 01/Aug/21 13:39
• Updated: 12/Nov/22 22:10

Description

yarnClient.getApplicationReport(appId) would return 2 state below:

1. YarnApplicationState (short as yarnState)
2. FinalApplicationStatus (short as finalState)

These 2 state may switch sequentially in practice, means (yarnState, finalState) as

(RUNNING, SUCCEEDED) would switch to (FINISHED, SUCCEEDED) finally.

For now, (yarnState, finalState)  as (RUNNING, SUCCEEDED)  would be identified as FAIL state combination in Livy, this result in Spark job unexpected fail in pratice.