SamWheating opened a new pull request #19950:
URL: https://github.com/apache/airflow/pull/19950
When a DagRun exceeds its `dagrun_timeout` value a few things happen:
- The run is marked as `failed`
- All currently-executing tasks are marked as `skipped`
- A line is logged in the scheduler logs: `INFO: Run $RUN_NUMBER of $DAG_ID
has timed-out`
This has caused some confusion amongst users as its hard to tell why running
tasks were killed without either:
1) cross-referencing the `dagrun_timeout` value with the execution time
2) reading the scheduler logs.
This PR adds additional messaging into the task logs when it can be inferred
that the task was killed due to a DagRun timeout. I'm not super happy with this
approach and would really appreciate some advice on other ways we can improve
the clarity around timeouts.
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
for more information.
In case of fundamental code change, Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
--
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]
