Log lifecycle stop() at info level#18640
Merged
Merged
Conversation
We have the lifecycle start() logged at info, but lifecycle close() is currently logged at debug. For inspectability, it's good to log this at info too. I was debugging why some close() hooks aren't invoked and this was helpful.
FrankChen021
approved these changes
Oct 16, 2025
riovic918data
pushed a commit
to riovic918data/druid
that referenced
this pull request
Jun 12, 2026
We have the lifecycle start() logged at info, but lifecycle close() is currently logged at debug. For inspectability, it's good to log this at info too. I was debugging why some close() hooks aren't invoked and this was helpful.
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
3 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.
We have the lifecycle
start()logged at info level, but the corresponding lifecycleclose()was logged at debug level. So log both lines at info so we can trace the whole lifecycle. I was debugging why some annotation-basedclose()hooks weren't invoked and this was helpful.This PR has: