-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
JetStream: incorrect consumer num_pending against stream with subjects ending in .>
#5608
Comments
Originally reported as a discussion in the Java repo: https://github.com/nats-io/nats.net/discussions/905 |
Can this be re-produced against main? |
I used the data with 2.10.17 the first time I was able to reproduce it. I only checked the older versions after Wally explained to me about stree and so I just tested starting with the version he suggested until I found the one it stopped working in. |
Have figured out the problem. The stree |
On a full wildcard `Match`, we were iterating through children but then also falling through to a regular continuation instead of returning, which meant that the `Match` callback could fire twice for the same filter. Fixes #5608. Signed-off-by: Neil Twigg <[email protected]>
Observed behavior
A new generic consumer reports more num_pending than actual messages in the stream.
Expected behavior
The consumer reports the correct num_pending.
Server version
2.10.10 or later. (Tested against 2.10.9 the information was reported correctly)
Steps to reproduce
Create a consumer against attached data,
nats consumer create
give it a name and all defaults. Look at the consumer info, it shows "Unprocessed Messages: 5,803". There are only 5670 messages.Notes
All subjects end with .> (dot greater) as in
OrchestrationStream_08fa7d3dcd644745bace255d2c76fbc2.>
Data
nats_cache.zip
stree_wildcard.zip
The text was updated successfully, but these errors were encountered: