Skip to content
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

[IMPROVED] Do not load all blocks for NumPending when delivery is LastPerSubject. #4885

Merged
merged 1 commit into from
Dec 15, 2023

Conversation

derekcollison
Copy link
Member

Update NumPending to use PSIM since block based fss is no longer present in >= 2.10.x
This was causing us to load all blocks to calculate NumPending for a new consumer with LastBySubject delivery.
Note this will be drastically improved with the new stree(ART) data structure in a future PR.

Signed-off-by: Derek Collison <derek@nats.io

@derekcollison
Copy link
Member Author

I see that TestJetStreamKVReductionInHistory is failing due to this change. Will fix tomorrow.

…ent.

This was causing us to load all blocks to calulate NumPending for a new consumer with LastBySubject delivery.

Note this will be drastically improved with stree(ART) in a later PR.

Signed-off-by: Derek Collison <derek@nats.io>
Copy link
Member

@wallyqs wallyqs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@derekcollison derekcollison merged commit 28a2a10 into main Dec 15, 2023
4 checks passed
@derekcollison derekcollison deleted the np-lastbysubj branch December 15, 2023 04:36
wallyqs added a commit that referenced this pull request Dec 15, 2023
Includes:

- Check all filterSubjects of consumers when purging a stream (#4873)
- Move tokenizing of subject after early returns (#4880)
- Move helper subjectInfo() to the file where it's used (#4881)
- JSAPI internal routing and reporting and Source and Mirror setup (#4884)
- Do not load all blocks for NumPending when delivery is LastPerSubject. (#4885)
- Detect corrupt psim subjects during recovery of index.db (#4890)
- Add 'certs' option to TLS block for multi-certs support (#4889)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants