Skip to content
This repository has been archived by the owner on Nov 29, 2024. It is now read-only.

doorman client can't connect new master server when old master is down forever #16

Open
BlueBlue-Lee opened this issue Jun 19, 2017 · 1 comment

Comments

@BlueBlue-Lee
Copy link

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
feature request

What happened:
Assume only have root level node, there are three doorman servers, one is master and other two are slave.

In doorman client, I configure the doorman master server addr. As the time going on, the master server is down, so new master is elected. However, doorman client don't know anything about it, doorman client just retry connect the configured addr continually and get failure response continually. So client rate limiting not work normally.

What you expected to happen or what your proposal is:
I think we should configure all addrs,including master addr and slave addr, in doorman client. So when master server is down forever, doorman client can retry connect with new addr.

@BlueBlue-Lee
Copy link
Author

@ryszard @josvisser Anyone there maintains this project ?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant