Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hi, another Prefect + K8S question here :slightly_smiling_face:

Like the previous post we're frequently seeing the message `No heartbeat detected...`  . Usually It happens in 2 situations:
• the pod that run the tasks gets evicted / OOM killed
• the pod was running on a preemptible node that gets removed and replaced.
Is there something on the k8s agent, k8s job specification, or something else to configure to allow k8s to reschedule the job and let prefect know about it, so that the flow would continue ?!

I am not sure `restartPolicy` will help here. Maybe use a DaskExecutor cuz Dask will restart the workers and retry the work?

yes `restartPolicy`  is not helping :confused:
Never used the DaskExecutor yet, I'll try it thanks !