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

Cherry-picks for 2.10.17-RC.7 #5572

Merged
merged 11 commits into from
Jun 21, 2024
Merged

Cherry-picks for 2.10.17-RC.7 #5572

merged 11 commits into from
Jun 21, 2024

Conversation

@neilalexander neilalexander changed the base branch from main to release/v2.10.17 June 20, 2024 09:42
Copy link
Member

@derekcollison derekcollison left a comment

Choose a reason for hiding this comment

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

LGTM

@neilalexander neilalexander changed the title Cherry-picks for 2.10.17 Cherry-picks for 2.10.17-RC.7 Jun 20, 2024
levb and others added 10 commits June 21, 2024 09:36
Otherwise long subjects could cause us to make the same reallocations
on each call to `tokenizeSubjectIntoSlice` without reusing the newly
sized underlying array for the next call.

Signed-off-by: Neil Twigg <[email protected]>
…subject transform (#5574)

In some cases a bad subject transform could still pass the validation
test that is part of the config check when updating a stream config, and
no error would be returned. Now return an error when trying to update a
stream config with a source that has a bad subject transform that is not
caught by the subject transform destination check in the stream config
check.

Improves #5571

---------

Signed-off-by: Jean-Noël Moyne <[email protected]>
…ing the session (#5575)

MQTT s.clear(): do not wait for JS responses when disconnecting the
session

Related to #5471

Previously we were making `jsa.NewRequest` as it is needed when
connecting a clean session. On disconnect, there is no reason to wait
for the response (and tie up the MQTT read loop of the client).

This should specifically help situations when a client app with many
MQTT connections and QOS subscriptions disconnects suddenly, causing a
flood of JSAPI deleteConsumer requests.

Test: n/a, not sure how to instrument for it.
This improves our updating of the outdated fblks when calling into
fs.numFilteredPending()

Signed-off-by: Derek Collison <[email protected]>

---------

Signed-off-by: Derek Collison <[email protected]>
Bug was that new wildcard matching code would not reverse start and stop, which is needed since we walk backwards.
Since they were not flipped as soon as start != stop, it would not enter the loop condition, e.g. start:1, stop:2 fails start >= stop.

Signed-off-by: Derek Collison <[email protected]>
Removed leaf-node related `TestXMQTTRetained...` test cases, they were
too flaky.
Should provide some deduplication of long subjects in memory when
message blocks are loaded in.

Signed-off-by: Neil Twigg <[email protected]>

---------

Signed-off-by: Neil Twigg <[email protected]>
Signed-off-by: Derek Collison <[email protected]>
Co-authored-by: Derek Collison <[email protected]>
@wallyqs wallyqs marked this pull request as ready for review June 21, 2024 21:50
@wallyqs wallyqs requested a review from a team as a code owner June 21, 2024 21:50
@wallyqs wallyqs merged commit 8ef49c4 into release/v2.10.17 Jun 21, 2024
3 checks passed
@wallyqs wallyqs deleted the neil/21017rc7 branch June 21, 2024 22:22
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.

5 participants