[jira] [Commented] (FLINK-18828) Terminate jobmanager process with zero exit code to avoid unexpected restarting by K8s

["Ufuk Celebi (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202044#comment-17202044 ] 

Ufuk Celebi commented on FLINK-18828:
-------------------------------------

[~trohrmann] [~fly_in_gis] Just noticed that this ticket has fix versions for 1.10 and 1.11. I think it would be better to only do this with a minor version upgrade (e.g. 1.12.0), because down stream users may rely on the current behaviour (I do).

> 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.12.0, 1.10.3, 1.11.3
>
>
> 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)