trlopes1974 commented on issue #41276: URL: https://github.com/apache/airflow/issues/41276#issuecomment-2271569597
Maybe, it makes some sense as we do not have that setting in the configuration. But, what is bothering me is WHY? why did it timeout after being queued? We have no exhaustion anywhere, not in CPU, Memory, pool slots, concurrency. I'd say that at the current time we have a very light system... So, I believe that the real question is, why is the task queued but never started? +-1year with some cleanups  All timeouts on our config: dagbag_import_timeout = 120.0 dag_file_processor_timeout = 180 default_task_execution_timeout = web_server_master_timeout = 120 web_server_worker_timeout = 120 smtp_timeout = 30 operation_timeout = 2 #task_adoption_timeout = 600 stalled_task_timeout = 0 # Example: visibility_timeout = 21600 # visibility_timeout = #worker_pods_pending_timeout = 300 default_timeout = 604800 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
