frsann commented on issue #30737: URL: https://github.com/apache/airflow/issues/30737#issuecomment-1515671978
We know the cause for the parsing errors and it has since been fixed, but the fact that the executor and the scheduler do not agree about the state of the task is a separate issue. We for example have alerting on high numbers of failed tasks, but this alert did not trigger due to this. Furthermore, as the DAG was in a running state it prevented future runs (unlike a failed DAG would have). But thanks for the link to a potential fix. It taught me about the `stalled_task_timeout` configuration, which seems like a good fallback if this issue persist. Looking forward to test the fix in 2.6.0 👍 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
