You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 29, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: