chore: log write stream opening at debug level - #363
Merged
Conversation
Signed-off-by: Matteo Merli <mmerli@apache.org>
This was referenced Jul 14, 2026
Merged
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
1 participant
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.
Motivation
Opened write streamis logged on every stream (re)establishment, once per shard, so at info level it adds noise during normal operation on clients with many shards. The related recovery details ("Replaying inflight writes on opened stream") are already at debug.Modification
Move the message to debug level, using the lambda form so the
pendingWritesattribute is not built when debug logging is disabled (same pattern as the surrounding debug logs).