[
https://issues.apache.org/jira/browse/FLINK-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252588#comment-17252588
]
Yang Wang commented on FLINK-18828:
-----------------------------------
Yes. This is still a valid problem in standalone perjob/application Kubernetes
deployment. Just like the description in this ticket, the K8s will restart the
JobManager pod when it terminated with non-zero exit code. Maybe we could add a
config option to allow the users specifying the exit code of failure
application. After then, for the standalone perjob/application K8s deployment,
we could configure it to zero to avoid unnecessary restarting.
> Terminate jobmanager process with zero exit code to avoid unexpected
> restarting by K8s
> --------------------------------------------------------------------------------------
>
> Key: FLINK-18828
> URL: https://issues.apache.org/jira/browse/FLINK-18828
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.10.1, 1.12.0, 1.11.1
> Reporter: Yang Wang
> Priority: Major
> Fix For: 1.13.0
>
>
> Currently, Flink jobmanager process terminates with a non-zero exit code if
> the job reaches the {{ApplicationStatus.FAILED}}. It is not ideal in K8s
> deployment, since non-zero exit code will cause unexpected restarting. Also
> from a framework's perspective, a FAILED job does not mean that Flink has
> failed and, hence, the return code could still be 0.
> > Note:
> This is a special case for standalone K8s deployment. For
> standalone/Yarn/Mesos/native K8s, terminating with non-zero exit code is
> harmless. And a non-zero exit code could help to check the job result quickly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
