19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
dagster-de
dagster-cube
gigs-freelance
dagster-wandb
dagster-machine-learning
dagster-bigquery
tools
dagster-dask
dagster-snowflake
dagster-releases
data-platform-design
events
dagster-serverless
dagster-noteable
introductions
dagster-airflow
dagster-cloud
random
dagster-dbt
faq-read-me-before-posting
dagster-airbyte
dagster-spatial
dagster-support
announcements
github-discussions
豆瓣酱帮
dagster-feedback
dagstereo
dagster-ecs
dagster-kubernetes
jobs
dagster-showcase
Title
p
Pablo Beltran
11/15/2022, 7:31 PMHey 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
j
johann
11/17/2022, 9:04 PMHi Pablo- we don’t currently support activeDeadlineSeconds well. We have an open issue for supporting timeouts: https://github.com/dagster-io/dagster/issues/3666
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) https://docs.dagster.io/deployment/run-monitoring