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
For a long running client, if the server loses the registration of a service or check via complete cluster data loss, a bug in the anti-entropy prevents that from being reconciled until the client is reloaded or restarted.
The text was updated successfully, but these errors were encountered:
* Refactor yaml to make port names obvious
* Split out server serfwan ports by udp/tcp
This is needed because in some cases Kubernetes will refuse udp traffic.
* Expose server serf WAN as hostPort
When `server.exposeGossipAndRPCPorts` is true, expose server's serf WAN
port as a host port on 8302. This is needed for specific cases where
serf attempts to use the WAN network because the advertise IP is the
host IP and so it will attempt to use hostIP and 8302.
This port does not need to be configurable (unlike serf LAN) because
clients don't expose a serf WAN port, only servers and so it won't
collide with client ports.
For a long running client, if the server loses the registration of a service or check via complete cluster data loss, a bug in the anti-entropy prevents that from being reconciled until the client is reloaded or restarted.
The text was updated successfully, but these errors were encountered: