-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Key shared subscription: hash ranges are not fully reported in stats #14073
Comments
Hi, @eolivelli I can help to fix it.~ |
@mattisonchao I know that @nicoloboschi is already working on a fix |
@eolivelli Ah, sorry. I just made a PR, or I'll close it... |
don't need to close it |
After having a more detailed look with @eolivelli, we've seen the version used by Enrico is a custom fork based on Pulsar 2.8.0 and it doesn't include #12212, which is the resolution to the problem @mattisonchao you can close the PR, the problem has been already fixed. Thanks |
The issue had no activity for 30 days, mark with Stale label. |
fixed by #12212 |
Describe the bug
When I run
pulsar-admin topics stats TOPIC-NAME
and I have a KeyShared subscription with stickyHashRanges, with many ranges, the stats are not fully reporting the ranges, it looks like that for each consumer they report only the last set of ranges assigned to each Consumer and for some Consumers the list is empty even if the Consumer set the range and it is actually consuming messages.There should be some bug here:
pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/HashRangeExclusiveStickyKeyConsumerSelector.java
Line 69 in 9abd6d3
Additional context
Pulsar 2.8.2
The text was updated successfully, but these errors were encountered: