allocator: voter constraint not satisfied when constraints are underspecified #122292
Labels
A-kv-distribution
Relating to rebalancing and leasing.
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
O-support
Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs
P-3
Issues/test failures with no fix SLA
T-kv
KV Team
Projects
Describe the problem
A voter constraint may not be satisfied when in an configuration where every existing voter is required to satisfy an all replica constraint and there isn't already a non-voter which would satisfy the voter constraint if promoted.
Note that this case is slightly different than #106559, where there already exists the correct number of replicas to satisfy every constraint, just the type is incorrect. Here, there are not enough replicas to satisfy the voter constraint regardless so a swap cannot take place. e.g.
Config:
Topology
Existing placement:
To Reproduce
See kvoli@f92433a
Expected behavior
Voter constraint is satisfied if possible.
Environment:
Additional context
Less voting replicas than desired in a locality.
Jira issue: CRDB-37790
The text was updated successfully, but these errors were encountered: