[IMPROVED] JSAPI internal routing and reporting and Source and Mirror setup #4884
Conversation
This file contains 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
…lowly back off retries til we hit maximum of 2m. Signed-off-by: Derek Collison <derek@nats.io>
…uests. This was due to the fact the the request was for an R1 consumer with a wildcard filter subject on a large subject space. This will be properly handled in a subsequent PR with a replacement for PSIM and calculating NumPending on a stream. For now, we are doing several changes in this CL. 1. Warn if the internal queue starts to back up past a limit (32 atm). 2. Use multiple Go routines in a pool to process on the other side. 3. Make sure to track inflight properly. We exposed it as an api usage stat for JetStream, but were not properly tracking. Signed-off-by: Derek Collison <derek@nats.io>
Signed-off-by: Derek Collison <derek@nats.io>
Signed-off-by: Derek Collison <derek@nats.io>
…rrors and sources after when we receive a response. Also cancel on a timeout since the consumer, even if created after, is of no use to us at this point. Signed-off-by: Derek Collison <derek@nats.io>
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
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.
A customer had an issue with JS api requests backing up in the internal queue we use to avoid blocking non-clients. The reason for the buildup was known due to time spent in NumPending calculations for R1 consumers with wildcard filtered subjects and large subject/key space. These consumers were being created from a large fan in stream with many sources.
Signed-off-by: Derek Collison derek@nats.io