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
A recent outage highlighted the need for mreg to support multiple LDAP servers for failover purposes.
Here's a dump from a discussion we had internally (names have been removed for privacy):
If your server location is even more dynamic than this, you may provide a function (or any callable object) that returns the URI. The callable is passed a single positional argument: request. You should assume that this will be called on every request, so if it’s an expensive operation, some caching is in order.
does it bind on every request? sounds expensive
for the actual check you could probably get away fairly cheap by using socket to check if a server is available, and implement some basic strategies like round robin and random selection
to avoid doing this on every single connection i would use cachetools.TTLCache
The text was updated successfully, but these errors were encountered:
A recent outage highlighted the need for mreg to support multiple LDAP servers for failover purposes.
Here's a dump from a discussion we had internally (names have been removed for privacy):
The text was updated successfully, but these errors were encountered: