-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Schedule backfills in the scheduler #42686
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Schedule backfills in the scheduler #42686
Conversation
(cherry picked from commit 2a581ab)
f05eca4 to
5763191
Compare
airflow/migrations/versions/0036_3_0_0_add_backfill_to_dag_run_model.py
Outdated
Show resolved
Hide resolved
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
|
It seems that this PR broke the "Non DB" tests for Always and CLI in https://github.com/apache/airflow/actions/runs/11200846409/job/31135117858?pr=42773 and on main. Any idea on how to fix this (easily) w/o reversion? |
I took a quick look but cannot reproduce locally. I am unavailable most of today. |
Thanks for checking. I saw it on multiple PRs and might be it is related to non DB tests and threading? Whereas interesting that it does not show-up in canary tests :-( I don't understand why, checked with different parallelism and not able to get this green locally. |
|
i'll look now |
This is part of AIP-78. Here we make it so for dag runs queued as part of a backfill, the scheduler will set them running in accordance with concurrency controls and schedule their tasks etc. Currently, backfill's concurrency is evaluated independently of DAG.max_active_runs. Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
This is part of AIP-78. Here we make it so for dag runs queued as part of a backfill, the scheduler will set them running in accordance with concurrency controls and schedule their tasks etc. Currently, backfill's concurrency is evaluated independently of DAG.max_active_runs. Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
This is part of AIP-78. Here we make it so for dag runs queued as part of a backfill, the scheduler will set them running in accordance with concurrency controls and schedule their tasks etc. Currently, backfill's concurrency is evaluated independently of DAG.max_active_runs. Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
This is part of AIP-78. Here we make it so for dag runs queued as part of a backfill, the scheduler will set them running in accordance with concurrency controls and schedule their tasks etc. Currently, backfill's concurrency is evaluated independently of DAG.max_active_runs. Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
(cherry picked from commit 2a581ab)