Hi, Afek! When a TaskManager is killed, JobManager will not be acknowledged until a heartbeat timeout happens. Currently, the default value of heartbeat.timeout is 50 seconds [1]. That's why it takes more than 30 seconds for Flink to trigger a failover. If you'd like to shorten the time a failover is triggered in this situation, you could decrease the value of heartbeat.timeout in flink-conf.yaml. However, if the value is set too small, heartbeat timeouts will happen more frequently and the cluster will be unstable. As FLINK-23403 [2] mentions, if you are using Flink 1.14 or 1.15, you could try to set the value to 10s.
You mentioned that it takes 5-6 minutes to restart the jobs. It seems a bit weird. How long does it take to deploy your job for a brand new launch? You could compact and upload the log of JobManager to Google Drive or OneDrive and attach the sharing link. Maybe we can find out what happens via the log. Sincerely, Zhilong [1] https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#heartbeat-timeout [2] https://issues.apache.org/jira/browse/FLINK-23403 On Thu, Feb 24, 2022 at 12:25 AM Afek, Ifat (Nokia - IL/Kfar Sava) < ifat.a...@nokia.com> wrote: > Hi, > > > > I am trying to use Flink checkpoints solution in order to support task > manager recovery. > > I’m running flink using beam with filesystem storage and the following > parameters: > > checkpointingInterval=30000 > > checkpointingMode=EXACTLY_ONCE. > > > > What I see is that if I kill a task manager pod, it takes flink about 30 > seconds to identify the failure and another 5-6 minutes to restart the jobs. > > Is there a way to shorten the downtime? What is an expected downtime in > case the task manager is killed, until the jobs are recovered? Are there > any best practices for handling it? (e.g. different configuration > parameters) > > > > Thanks, > > Ifat > > >
