MINOR: Add startup-duration logging to help with Kafka startup performance tuning #20959
+6
−2
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.
Sometimes we need to know how long Kafka takes to start in order to make certain decisions—for example, tuning configuration parameters or estimating how much time operations will require. However, it’s quite inconvenient to manually look for the timestamp of the first log line and then the first log line hint the server has started, and calculate the difference.
So this PR adds a direct log output for the startup duration.
Log the total startup time after successful server startup:
"Kafka startup completed in ${startupDurationMs} ms"Benefits: