[
https://issues.apache.org/jira/browse/FLINK-12302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848987#comment-16848987
]
Gary Yao commented on FLINK-12302:
----------------------------------
[~lamber-ken] Thanks for your example. However, I am still not able to
reproduce this (emr-5.23.0, Amazon Hadoop 2.8.5). I manually killed the AM
after submission, and triggered another application attempt. Find attached the
logs:
[^jobmanager-05-27.log]
Maybe you can attach logs as well?
Submission command:
{code}
HADOOP_CLASSPATH=`hadoop classpath` bin/flink run -m yarn-cluster -d -c
com....TestDemo ../testjob-1.0-SNAPSHOT.jar
{code}
> 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, jobmanager-05-27.log, screenshot-1.png,
> screenshot-2.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)
