XD-DENG opened a new pull request, #27611: URL: https://github.com/apache/airflow/pull/27611
Currently there is no try-catch logic when `pod_mutation_hook` is called in the Kubernetes Executor. So if there is any error/exception during the execution of the `pod_mutation_hook` user created, the whole executor/scheduler will crash. Such error may happen: - user who authored the `pod_mutation_hook` made an error inside. - if there is any code inside the `pod_mutation_hook` encounters transient error (e.g. it queries DB and the DB gives a timeout error). - ... you name it. It can simply go wrong. This PR aims to make Kubernetes Executor & Scheduler more resilient to such error during PMH execution (current behavior, directly crashing, is a bit scary) --- **^ 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]
