jhtimmins opened a new pull request #11589:
URL: https://github.com/apache/airflow/pull/11589


   In order to further reduce intra-dag task scheduling lag we add an
   optimization: when a task has just finished executing (success or
   failure) we can look at the downstream tasks of just that task, and then
   make scheduling decisions for those tasks there -- we've already got the
   dag loaded, and we know they are likely actionable as we just finished.
   
   We should set tasks to scheduled if we can (but no further, i.e. not to
   queued, as the scheduler has to make that decision with info about the
   Pool usage etc.).
   
   Co-authored-by: Ash Berlin-Taylor <ash_git...@firemirror.com>
   
   <!--
   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/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/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/master/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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to