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] Updating of a large fleet of leafnodes. #4117

Merged
merged 1 commit into from May 1, 2023

Conversation

derekcollison
Copy link
Member

When a fleet of leafnodes are isolated (not routed but using same cluster) we could do better at optimizing how we update the other leafnodes since if they are all in the same cluster and we know we are isolated we can skip.

We can improve further in 2.10.

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

…ster) we could do better at optimizing how we update the other leafnodes.

Signed-off-by: Derek Collison <derek@nats.io>
@derekcollison derekcollison requested a review from a team as a code owner May 1, 2023 00:18
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 7ad2dd2 into main May 1, 2023
2 checks passed
@derekcollison derekcollison deleted the leafnode-fleet branch May 1, 2023 00:32
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