Skip to content

Use client-local for default leader locator strategy #110

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.

Sign up for GitHub

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

Jump to bottom
Closed
acogoluegnes opened this issue May 3, 2022 · 1 comment
Closed

Use client-local for default leader locator strategy #110

acogoluegnes opened this issue May 3, 2022 · 1 comment
Assignees
@acogoluegnes
Labels
invalid This doesn't seem right usability
Milestone
0.6.0

Comments

@acogoluegnes
Copy link
Contributor

See rabbitmq/rabbitmq-server#4442 for background.
@acogoluegnes acogoluegnes added this to the 0.6.0 milestone May 3, 2022
@acogoluegnes acogoluegnes self-assigned this May 3, 2022
@acogoluegnes acogoluegnes added the invalid This doesn't seem right label May 3, 2022
@acogoluegnes
Copy link
Contributor Author

We should stick to least-leaders (i.e. balanced), otherwise we'll end up with the leaders on the same node with client-local as the locator connection handles all the creations.

acogoluegnes added a commit that referenced this issue May 3, 2022
@acogoluegnes
Use least-leaders for default leader locator strategy
d978bde 
References rabbitmq/rabbitmq-server#4442.

References #110
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@acogoluegnes acogoluegnes

Labels
invalid This doesn't seem right usability
Projects
None yet
Milestone
0.6.0
Development

No branches or pull requests
1 participant
@acogoluegnes