[
https://issues.apache.org/jira/browse/FLINK-12302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839243#comment-16839243
]
Gary Yao commented on FLINK-12302:
----------------------------------
[~lamber-ken] I am not able to reproduce this on Flink 1.8. I am submitting the
SocketWindowWordCount from the examples with a non-existing hostname. The final
status is {{FAILED}}. You wrote that you are using Flink 1.6.3 but the ticket
mentions 1.8.3 as the affected version. Can you elaborate on this?
> 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
> Labels: pull-request-available
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
