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

• Type: Improvement
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Affects Version/s: 1.10.1, 1.11.1, 1.12.0
• Component/s: Runtime / Coordination
• Labels: auto-deprioritized-major auto-deprioritized-minor
• Assignee: Unassigned
• Reporter: Yang Wang
• Created: 05/Aug/20 11:28
• Updated: 27/Nov/21 23:06

Description

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.

Issue Links

• is related to: FLINK-10743 Use 0 processExitCode for ApplicationStatus.CANCELED