You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "lamber-ken (JIRA)" <ji...@apache.org> on 2019/04/25 06:09:00 UTC
[jira] [Updated] (FLINK-12302) Fixed the wrong finalStatus of yarn
application when application finished
[ https://issues.apache.org/jira/browse/FLINK-12302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lamber-ken updated FLINK-12302:
-------------------------------
Summary: Fixed the wrong finalStatus of yarn application when application finished (was: Fixed the wrong finalStatus of yarn application when job not finished)
> Fixed the wrong finalStatus of yarn application when application finished
> -------------------------------------------------------------------------
>
> Key: FLINK-12302
> URL: https://issues.apache.org/jira/browse/FLINK-12302
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Affects Versions: 1.8.0
> Reporter: lamber-ken
> Assignee: lamber-ken
> Priority: Minor
> Fix For: 1.9.0
>
> Attachments: fix-bad-finalStatus.patch, image-2019-04-23-19-56-49-933.png, spslave4.bigdata.ly_23951, spslave5.bigdata.ly_20271
>
>
> flink job(flink-1.6.3) failed in per-job yarn cluste mode, the resourcemanager of yarn rerun the job.
> when the job failed again, the application while finish, but the finalStatus is +UNDEFINED,+ It's better to show state +FAILED+
> !image-2019-04-23-19-56-49-933.png!
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)