Consul leadership selection in cluster when consul servers are down
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 43
Description
#### Overview of the Issue
When in cluster of 3 Consul servers 2 servers are down and then 1 goes up (so we have 2 Servers Up), they are not able to select leader of cluster.
It worked well in 1.4.4 but when we tried to verify this scenario in 1.7.1 it failed.
#### Reproduction Steps
Cluster of 3 consul servers (also -bootstrap-expect = 3).
Lets say we have Servers: A (Leader), B , C
Stop A --> Servers: B(Leader), C
Stop B --> Servers C
Start A --> Servers A,C
These 2 servers didn’t succeed to select leader of the cluster back , since B was last leader and it is down.
In the case that 3) Start B --> Servers B,C and B keeps to be leader.
### Operating system and Environment details
Windows. Consul 1.7.1
Is this behavior valid? Should they able to select leader of the cluster in the case of 2 from 3 servers are up?
Contributor guide
Assessment
This issue has not been assessed yet.