Re-resolve server names on connection failure

[EmpireJones]

Currently the server names are only resolved once, to optimize performance. However, this doesn't support dynamic environments well in which the name should be re-resolved.

I think that I can work around this by wrapping the library calls, and creating a new connection upon error (or maybe creating something which detects name resolution changes), but this doesn't seem ideal.

I considered periodically running SetServers, but I believe the ServerList isn't public in the client.

[patrickeasters]

I'm facing this as well. I have some workarounds in place, but it'd be nice to be able to update that server list or have it resolve the name each time it connects and let the OS handle DNS TTLs.

[anjmao]

Hi, if you run memcache in kubernetes we implemented https://github.com/castai/k8s-memcache-selector It watches memcache k8s endpoints and updates server list.