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 Dec 20, 2018. It is now read-only.
We're going to deploy bud on multiple boxes in different DCs for DNS round-robin failover.
In the docs is a hint that ticket rotation will be a problem in this case (if I understand correctly). What is the setup for synchronized ticket rotation?
And: will there be any other problems?
The text was updated successfully, but these errors were encountered:
Guess, I can amend the node.js wrapper of bud, and make it expose this key rotation APIs using plain HTTP. But someone will need to start them, and to coordinate ticket rotation between multiple servers.
Does it make sense?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We're going to deploy bud on multiple boxes in different DCs for DNS round-robin failover.
In the docs is a hint that ticket rotation will be a problem in this case (if I understand correctly). What is the setup for synchronized ticket rotation?
And: will there be any other problems?
The text was updated successfully, but these errors were encountered: