Change log level from info to debug for Edge job fetch - #68736
Merged
Conversation
boring-cyborg
Bot
added
area:providers
provider:edge
potiuk
added
the
ready for maintainer review
henry3260
reviewed
Jul 1, 2026
Contributor
Author
|
@henry3260 Sorry for the delay, I've updated the docs as suggested. |
This changes the log level of the "No new job to process" message in `fetch_and_run_job()` from `logger.info` to `logger.debug`.
*Why*: An idle edge worker emits this message every job_poll_interval seconds for as long as no work is queued. In many deployments, workers spend the majority of their time idle — that's by design, since edge workers are often provisioned for bursty or on-demand workloads. The result is that this single message dominates the worker logs, drowning out genuinely useful INFO-level entries like job starts, completions, state changes, and heartbeat events.
Per Python's logging conventions, INFO should communicate "confirmation that things are working as expected" — meaningful milestones and state transitions. An idle worker having nothing to do is the expected steady state, not a notable event. By contrast, DEBUG is the correct level for routine operational chatter useful only when actively troubleshooting.
For comparison, the line immediately above it already uses the right level: logger.debug("Attempting to fetch a new job..."). The "no job found" outcome is the other half of the same operation and should match.
Impact: No behaviour change. Operators who want to see these messages can still set the edge worker log level to DEBUG. Everyone else gets cleaner logs at the default INFO level.
dheerajturaga
approved these changes
Jul 10, 2026
dheerajturaga
left a comment
dheerajturaga
left a comment
Member
There was a problem hiding this comment.
I agree that useful information can get buried deep with the no new job message. The changes look good
joshuabvarghese
pushed a commit
to joshuabvarghese/airflow
that referenced
this pull request
Jul 16, 2026
* Change log level from info to debug for Edge job fetch
This changes the log level of the "No new job to process" message in `fetch_and_run_job()` from `logger.info` to `logger.debug`.
*Why*: An idle edge worker emits this message every job_poll_interval seconds for as long as no work is queued. In many deployments, workers spend the majority of their time idle — that's by design, since edge workers are often provisioned for bursty or on-demand workloads. The result is that this single message dominates the worker logs, drowning out genuinely useful INFO-level entries like job starts, completions, state changes, and heartbeat events.
Per Python's logging conventions, INFO should communicate "confirmation that things are working as expected" — meaningful milestones and state transitions. An idle worker having nothing to do is the expected steady state, not a notable event. By contrast, DEBUG is the correct level for routine operational chatter useful only when actively troubleshooting.
For comparison, the line immediately above it already uses the right level: logger.debug("Attempting to fetch a new job..."). The "no job found" outcome is the other half of the same operation and should match.
Impact: No behaviour change. Operators who want to see these messages can still set the edge worker log level to DEBUG. Everyone else gets cleaner logs at the default INFO level.
* Update log message in docs
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
4 participants
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.
This changes the log level of the "No new job to process" message in
fetch_and_run_job()fromlogger.infotologger.debug.Why: An idle edge worker emits this message every job_poll_interval seconds for as long as no work is queued. In many deployments, workers spend the majority of their time idle — that's by design, since edge workers are often provisioned for bursty or on-demand workloads. The result is that this single message dominates the worker logs, drowning out genuinely useful INFO-level entries like job starts, completions, state changes, and heartbeat events.
Per Python's logging conventions, INFO should communicate "confirmation that things are working as expected" — meaningful milestones and state transitions. An idle worker having nothing to do is the expected steady state, not a notable event. By contrast, DEBUG is the correct level for routine operational chatter useful only when actively troubleshooting.
For comparison, the line immediately above it already uses the right level: logger.debug("Attempting to fetch a new job..."). The "no job found" outcome is the other half of the same operation and should match.
Impact: No behaviour change. Operators who want to see these messages can still set the edge worker log level to DEBUG. Everyone else gets cleaner logs at the default INFO level.
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.