Add docs for multi-team triggerer support#67608
Conversation
Add a `Team-scoped Triggerer` section to the multi-team documentation covering the `--team-name` CLI argument, behavior for team-scoped vs global triggerers, interaction with `--queues`, and an example deployment. Add a tip in the deferring docs pointing users toward `--team-name` as the native multi-team solution alongside the existing `--queues` docs. Remove `Async support` from the `Work in Progress` list since team-scoped triggerer support is now implemented/in PR.
| Team-scoped Triggerer | ||
| --------------------- | ||
|
|
||
| When Multi-Team mode is enabled, the triggerer can be scoped to a specific team using the ``--team-name`` CLI argument. A team-scoped triggerer only processes deferred tasks (triggers) belonging to that team's Dags. This allows teams to run isolated triggerer instances with independent capacity and failure domains. |
There was a problem hiding this comment.
Should be? Otherwise team triggers aren't going to run, right?
| When Multi-Team mode is enabled, the triggerer can be scoped to a specific team using the ``--team-name`` CLI argument. A team-scoped triggerer only processes deferred tasks (triggers) belonging to that team's Dags. This allows teams to run isolated triggerer instances with independent capacity and failure domains. | |
| When Multi-Team mode is enabled, a triggerer should be scoped to each specific team using the ``--team-name`` CLI argument. A team-scoped triggerer processes deferred tasks (triggers) belonging to that team's Dags. This allows teams to run isolated triggerer instances with independent capacity and failure domains. |
|
|
||
| .. note:: | ||
|
|
||
| If you use both ``--team-name`` and ``--queues``, ensure that each combination of team and queue has at least one triggerer running, or triggers matching that combination will remain unassigned until one starts. |
There was a problem hiding this comment.
This is true for each individually as well right?
| Example Deployment | ||
| ^^^^^^^^^^^^^^^^^^ | ||
|
|
||
| A deployment with two teams and a shared set of Dags with no team: | ||
|
|
||
| .. code-block:: bash | ||
|
|
||
| # Team-scoped triggerers | ||
| airflow triggerer --team-name team_a | ||
| airflow triggerer --team-name team_b | ||
|
|
||
| # Global triggerer for Dags without a team | ||
| airflow triggerer | ||
|
|
There was a problem hiding this comment.
This feels superfluous to me, I'd just drop it.
|
@ramitkataria — There are 3 unresolved review thread(s) on this PR from Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you. |
4 participants
Add a
Team-scoped Triggerersection to the multi-team documentation covering the--team-nameCLI argument, behavior for team-scoped vs global triggerers, interaction with--queues, and an example deployment.Add a tip in the deferring docs pointing users toward
--team-nameas the native multi-team solution alongside the existing--queuesdocs.Remove
Async supportfrom theWork in Progresslist since team-scoped triggerer support is now implemented/in PR.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.