repl-chris opened a new pull request, #23432:
URL: https://github.com/apache/airflow/pull/23432

   <!--
   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 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/
   -->
   Celery can lose tasks on worker shutdown, causing airflow to just wait on 
them indefinitely (may be related to 
https://github.com/celery/celery/issues/7266). This PR detects these "hung" 
tasks and sets them back to `SCHEDULED` state so the scheduler can queue them 
up again.
   
   Closes: #19699
   
   This is basically a resurrection of 
[PR19769](https://github.com/apache/airflow/pull/19769) which was 
[reverted](https://github.com/apache/airflow/pull/21556) because no one could 
reproduce/test it. We can reproduce the problem reliably in an isolated test 
environment, so we were able to test this fairly thoroughly.
   
   cc: @ephraimbuddy @kristoffern @kaxil 
   
   ---
   **^ 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 a 
newsfragement file, named `{pr_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]

Reply via email to