Pablo Beltran

11/15/2022, 7:31 PM
Hey there! I have a job where I have configured the activeDeadlineSeconds to be 600. However the job has been running for 10 hours. When I describe the job in k8s I see: ''' Active Deadline Seconds: 600s Pods Statuses: 0 Active / 0 Succeeded / 1 Failed "'' So it seems the pod failed but the job is still active in dagster


11/17/2022, 9:04 PM
Hi Pablo- we don’t currently support activeDeadlineSeconds well. We have an open issue for supporting timeouts:
For the case of a Dagster job running after the underlying pod has failed, I would expect that enabling run monitoring would solve this (it polls the job status and would mark the run as failed)