Change edge worker heartbeat message from info to debug - #72197
Merged
potiuk merged 1 commit intoAug 28, 2026
Merged
Conversation
KidAmnesiac1
requested review from
dheerajturaga,
jscheffl and
shubhamraj-git
as code owners
August 28, 2026 13:04
potiuk
approved these changes
Aug 28, 2026
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.
Change log level from info to debug for Edge worker status requests
The "Request to get status of Edge Worker received." message in
signal_status() drops from info to debug.
Why: this line fires whenever someone runs
airflow edge status. Thatcommand just asks the worker what it's doing and prints the answer — it
doesn't change anything about the worker. It's also the sort of command
people put in a loop: health checks, monitoring scripts, or an operator
keeping an eye on a worker that's draining. Every one of those calls
leaves an info line in the log saying someone asked a question.
The other half of the same if-statement makes the point. When a
maintenance marker is present the worker really does change state, and
that branch logs at info — which is right. Answering a status query
isn't a change, so it shouldn't sit at the same level.
The command sending the signal already logs at debug on its side
("Sending SIGUSR2 to worker pid ..."), so this just gets both ends to
agree.
No behaviour change. The status file is written exactly as before and
airflow edge statusprints the same thing. If you want these messagesback, set the edge worker log level to DEBUG.
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.