Skip to content

storage: RelocateRange doesn't handle edge cases properly #29130

@benesch

Description

@benesch

// TODO(benesch): RelocateRange needs to be made more robust. It cannot
// currently handle certain edge cases, like multiple stores on one node. It
// also adds all new replicas before removing any old replicas, rather than
// performing interleaved adds/removes, resulting in a moment where the
// number of replicas is potentially double the configured replication
// factor.

// This is best-effort; if replication queues are enabled and a change in
// membership happens at the same time, there will be errors.

Metadata

Metadata

Assignees

Labels

A-kv-distributionRelating to rebalancing and leasing.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions