Flink job restarted from empty state when execution.shutdown-on-application-finish is false

[Gyula Fóra <gy...@apache.org>]

Hi Devs!

I ran into a concerning situation and would like to hear your thoughts on
this.

I am running Flink 1.15 on Kubernetes native mode (using the operator but
that is besides the point here) with Flink Kubernetes HA enabled.

We have set
*execution.shutdown-on-application-finish = false*

I noticed that if after the job failed/finished, if I kill the jobmanager
pod (triggering a jobmanager failover), the job would be resubmitted from a
completely empty state (as if starting for the first time).

Has anyone encountered this issue? This makes using this config option
pretty risky.

Thank you
Gyula

Re: Flink job restarted from empty state when execution.shutdown-on-application-finish is false

[Gyula Fóra <gy...@apache.org>]

I have opened a JIRA: https://issues.apache.org/jira/browse/FLINK-27569
with more details, logs and screenshots.

Gyula

On Wed, May 11, 2022 at 7:03 AM Gyula Fóra <gy...@apache.org> wrote:

> Hi Devs!
>
> I ran into a concerning situation and would like to hear your thoughts on
> this.
>
> I am running Flink 1.15 on Kubernetes native mode (using the operator but
> that is besides the point here) with Flink Kubernetes HA enabled.
>
> We have set
> *execution.shutdown-on-application-finish = false*
>
> I noticed that if after the job failed/finished, if I kill the jobmanager
> pod (triggering a jobmanager failover), the job would be resubmitted from a
> completely empty state (as if starting for the first time).
>
> Has anyone encountered this issue? This makes using this config option
> pretty risky.
>
> Thank you
> Gyula
>