Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Anti-Entropy does not properly handle case with client state and lost-server state #839

Closed
armon opened this issue Apr 3, 2015 · 0 comments · Fixed by #850
Closed

Anti-Entropy does not properly handle case with client state and lost-server state #839

armon opened this issue Apr 3, 2015 · 0 comments · Fixed by #850
Labels
type/bug Feature does not function as expected
Milestone
0.5.1

Comments

@armon
Copy link
Member

armon commented Apr 3, 2015

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.
@armon armon added the type/bug Feature does not function as expected label Apr 3, 2015
This was referenced Apr 8, 2015
Merged
Closed
@armon armon modified the milestone: 0.5.1 Apr 9, 2015
duckhan pushed a commit to duckhan/consul that referenced this issue Oct 24, 2021
@lkysow
Server wan ports (hashicorp#839)
ae54c22 
* 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.
@ekmixon ekmixon mentioned this issue May 14, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/bug Feature does not function as expected
Projects
None yet
Milestone
0.5.1
Development

Successfully merging a pull request may close this issue.

Anti-entropy sync services/checks missing entirely from Consul hashicorp/consul
1 participant
@armon