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

Proposal: Broker usage check on reconnect #166

Open
valcryst opened this issue Dec 17, 2022 · 0 comments
Open

Proposal: Broker usage check on reconnect #166

valcryst opened this issue Dec 17, 2022 · 0 comments

Comments

@valcryst
Copy link

Right now it seems that the usage/selection process on reconnect gets only triggered after 15-20s.
While i understand that this was probably introduced to improve reconnect time after dialup/connection loss.

This behaviour leads to a problem in case you have atleast two brokers running on different machines.
If you do maintenance on one of them and shutdown the broker for a while, the clients will move to the
remaining broker. When you finish maintenance and start the broker, you will have to shutdown all other
brokers for atleast 30-40s to trigger selection on all clients, otherwise the clients wont move to the other brokers.

Would it be possible to have broker selection on every reconnect or would it be better to have the broker send a "restarted"
signal to trigger selection on the client ?

Kindly Regards

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

No branches or pull requests

1 participant