MINOR : Corrected the stdout parsing in ShareConsumerPerformanceService#21473
Merged
AndrewJSchofield merged 1 commit intoapache:trunkfrom Feb 13, 2026
Merged
Conversation
github-actions
bot
added
triage
chirag-wadhwa5
changed the title
chirag-wadhwa5
changed the title
AndrewJSchofield
added
KIP-932
AndrewJSchofield
approved these changes
Feb 13, 2026
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
2 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.
The ShareConsumerPerformanceService runs the
kafka-share-consumer-perf-test.shscript and parses its stdout tofurther report the performance numbers. The script's output format is as
follows ->
start.time, end.time, data.consumed.in.MB, MB.sec, nMsg.sec, data.consumed.in.nMsg, fetch.time.msOne of the fields it tried to read is
records_per_sec. As per thecurrent code, it parses the wrong value (instead of reading the 5th
value (nMsg.sec), it reads the 6th one (data.consumed.in.nMsg)). This PR
corrects that.
Reviewers: Andrew Schofield aschofield@confluent.io