Add key-shared consumer range to internal topic stats. - #8567
Conversation
|
/pulsarbot run-failure-checks |
|
@codelipenghui can you please help take a look |
|
@MarvinCai I think it's better to add the consumer-related stats into the A consumer might be assigned to multiple |
|
Update to put this info in ConsumerStats and it's now part of topic-stats, example output: |
codelipenghui
left a comment
There was a problem hiding this comment.
The change looks good to me.
Is it better to use "[0, 65535]" to instead ''0--65535"? "[" or "]" usually understood to include. Of cause, if use "[]" the output topic stats looks like the followings
keyHashRanges: [[0, 123], [124, 65535]]
This is more like individuallyDeletedMessages in the topic stats-internal. This might be a good choice to keep consistent with individuallyDeletedMessages
|
make sense, the key range is more like interval and it's better we clearly specify if it's open or closed interval, updated the string format. |
|
/pulsarbot run-failure-checks |
1 similar comment
|
/pulsarbot run-failure-checks |
Expose consumer range information in topic internal stats
Fixes #5752
Master Issue: #4077
Motivation
Expose consumer range information in topic internal stats.
sample output
Modifications
Verifying this change
This change added tests and can be verified as follows:
Does this pull request potentially affect one of the following parts:
If
yeswas chosen, please highlight the changesDocumentation