[
https://issues.apache.org/jira/browse/FLINK-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178787#comment-17178787
]
Till Rohrmann commented on FLINK-18891:
---------------------------------------
[~happylife], it is because the {{FlinkYarnSessionCli}} will overwrite this
value depended on the command line options you specify when calling the Flink
cli. In order to submit a detached yarn per job mode job you have to call
{{bin/flink run -m yarn-cluster -d job.jar}}. The important bit is {{-d}} which
says that the job should be deployed in detached mode.
> flink job failed but yarn application still running via yarn-per-job mode
> -------------------------------------------------------------------------
>
> Key: FLINK-18891
> URL: https://issues.apache.org/jira/browse/FLINK-18891
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Affects Versions: 1.10.1
> Reporter: Peng
> Priority: Critical
>
> Run a flink stream sql job via yarn-per-job mode, flink-conf.yaml like below:
> {code:java}
> execution.target: yarn-per-job
> restart-strategy: fixed-delay
> restart-strategy.fixed-delay.attempts: 3
> restart-strategy.fixed-delay.delay: 2s
> {code}
>
> After restarting job 3 times, the flink job status is FAILED, but yarn
> application state is still Running. Should the yarn application state be
> Finished when flink job FAILED? Thanks.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
