[
https://issues.apache.org/jira/browse/LIVY-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-865:
----------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If
you feel this is moved out inappropriately, feel free to provide justification
and reset the Fix Version to 0.9.0.
> Livy identify valid yarn state of batch session as FAIL unexpectedly
> --------------------------------------------------------------------
>
> Key: LIVY-865
> URL: https://issues.apache.org/jira/browse/LIVY-865
> Project: Livy
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.7.0
> Reporter: Du Ripeng
> Priority: Major
> Fix For: 0.10.0
>
> Attachments: image-2021-08-01-21-39-02-970.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> yarnClient.getApplicationReport(appId) would return 2 state below:
> # YarnApplicationState (short as yarnState)
> # 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.
> !image-2021-08-01-21-39-02-970.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
