Repository navigation
Run team tasks on the team executor when named by class or path - #75362
Merged
o-nikolas merged 2 commits intoOct 22, 2026
Merged
Conversation
1 task done
Contributor
|
Helper method |
With multi-team enabled, a team task that names its executor by class
name or module path (e.g. executor="CeleryExecutor") is documented to
run on its team's executor of that class. Only the global alias should
reach the global executor ("Aliasing Executors Across Teams" in the
multi-team docs).
The scheduler took the first matching executor instead, and global
executors are always listed before team ones. So these tasks silently
ran on the shared global executor, outside the team boundary, and
anything resolving executors the documented way (such as reading live
task logs) looked in the wrong place.
The scheduler and task log reading each had their own copy of the rule for picking a task's executor. The copies already drifted apart once: the scheduler picked a global executor where log reading picked the team's. Sharing ExecutorLoader.resolve_executor_name means a task's logs are always read from the executor it ran on. Scheduler test mocks now put an executor's team on its name too, as the executor loader does, because the helper reads the team from the name.
o-nikolas
force-pushed
the
onikolas/scheduler-team-executor-first
branch
from
October 22, 2026 15:53
0f97bdb to
e66b9fe
Compare
seanghaeli
approved these changes
Oct 22, 2026
vincbeck
approved these changes
Oct 22, 2026
Contributor
Backport successfully created: v3-4-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
vatsrahul1001
pushed a commit
that referenced
this pull request
Oct 23, 2026
…r path (#75362) (#75436) With multi-team enabled, a team task that names its executor by class name or module path (e.g. executor="CeleryExecutor") is documented to run on its team's executor of that class. Only the global alias should reach the global executor ("Aliasing Executors Across Teams" in the multi-team docs). The scheduler took the first matching executor instead, and global executors are always listed before team ones. So these tasks silently ran on the shared global executor, outside the team boundary, and anything resolving executors the documented way (such as reading live task logs) looked in the wrong place. (cherry picked from commit 0abd161) Co-authored-by: Niko Oliveira <onikolas@apache.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With multi-team enabled, a team task that names its executor by class name or module path (e.g. executor="CeleryExecutor") is documented to run on its team's executor of that class. Only the global alias should reach the global executor ("Aliasing Executors Across Teams" in the multi-team docs).
The scheduler took the first matching executor instead, and global executors are always listed before team ones. So these tasks silently ran on the shared global executor, outside the team boundary, and anything resolving executors the documented way (such as reading live task logs) looked in the wrong place.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.