Consul Cluster not sync
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
In a Consul cluster with three nodes, services are not synchronizing. For instance, a service registered through the first node at 10.10.10.1 can only be deleted from the same node at 10.10.10.1. Attempting to delete it from the second node at 10.10.10.2 results in an error indicating that the service cannot be found.
I checked the data directory, and the services directory does not synchronize.
Contributor guide
Research direction
Start by reproducing the three-node Consul cluster scenario described in the issue, registering through 10.10.10.1 and attempting deletion through 10.10.10.2. Inspect the data directory and services directory while comparing node state; the issue is resolved when service registration and deletion are synchronized across nodes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100