Subject: Job recovers from an old dangling CheckPoint in case of Job Cluster based Flink pipeline


So there a re 2 scenerios

1. If JM goes down ( exits ) and k8s re launches the Job Cluster ( the JM
),  it is using the exact command, the JM was brought up in the first place.

2. If the pipe is restarted for any other reason by the JM ( the JM has not
exited but  *Job Kafka-to-HDFS (00000000000000000000000000000005) switched
from state RESTARTING to CREATED. ) , * it does the right thing.

Not what is the right way to handle 1. apart from
spec:

  restartPolicy: Never

and manually restart...
On Sat, Jun 29, 2019 at 9:25 AM Vishal Santoshi <[EMAIL PROTECTED]>
wrote: