pankajastro opened a new pull request, #31274: URL: https://github.com/apache/airflow/pull/31274
In the case of multiple schedulers lots of tasks running If schedulers restart a bit quickly some cases it sets the wrong task status. In this PR, I'm changing some checks so that if the pod status is non-terminal then set the task status to Failed only if the pod event type is DELETED and POD_EXECUTOR_DONE_KEY is in the pod label. **Example screenshot before changes** <img width="1374" alt="Screenshot 2023-05-14 at 2 55 02 AM" src="https://github.com/apache/airflow/assets/98807258/960ece72-af58-4677-895c-ee88b6abb17e";> **Example screenshot after changes** <img width="1224" alt="Screenshot 2023-05-14 at 2 49 30 AM" src="https://github.com/apache/airflow/assets/98807258/d0d5a5f8-d2d5-42a1-8228-8b28f6ba8acc";> <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ 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 changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+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 a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments). -- 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]
