-
Notifications
You must be signed in to change notification settings - Fork 3.1k
[ISSUE #6560] Avoid junk Kafka log records during producer initialization. #7150
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
Merged
Aias00
merged 4 commits into
apache:master
from
sunnysabor:fix/logging-kafka-init-without-record
Sep 21, 2026
+30
−28
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
ada4544
fix logging-kafka : avoid sending a record during initialization.
sunnysabor 4fb3e72
Merge branch 'master' into fix/logging-kafka-init-without-record
Aias00 fa44306
Merge branch 'master' into fix/logging-kafka-init-without-record
Aias00 7fc00fd
Merge branch 'master' into fix/logging-kafka-init-without-record
Aias00 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion (non-blocking): this call blocks until metadata arrives or
max.block.mselapses (60 s by default), andinitClient0is reached fromLoggingKafkaPluginDataHandler#doRefreshConfig, i.e. the config-sync path - an unreachable broker would park it for up to a minute per refresh.The previous
send()was not better here (KafkaProducer#sendcallswaitOnMetadatawith the same budget), so this is not a regression, just worth bounding now that fetching metadata is the whole point of the probe. Since kafka-clients 3.9.2 has nopartitionsFor(String, Duration)overload (verified with javap against the exact version this reactor depends on), the only lever is:Also worth considering: when the topic does not exist and auto-creation is disabled,
partitionsForsimply returns an empty list instead of raising, so a mistyped topic still reports a successful init.