Vlad Lazar f8ac3b0e0e storcon: use attached shard counts for initial shard placement (#8061) ...

## Problem
When creating a new shard the storage controller schedules via
Scheduler::schedule_shard. This does not take into account the number of
attached shards. What it does take into account is the node affinity:
when a shard is scheduled, all its nodes (primaries and secondaries) get
their affinity incremented.

For two node clusters and shards with one secondary we have a
pathological case where all primaries are scheduled on the same node.
Now that we track the count of attached shards per node, this is trivial
to fix. Still, the "proper" fix is to use the pageserver's utilization
score.

Closes https://github.com/neondatabase/neon/issues/8041

## Summary of changes
Use attached shard count when deciding which node to schedule a fresh
shard on.

2024-06-20 17:32:01 +01:00

..

migrations

Clean up 'attachment service' names to storage controller (#7326)

2024-04-05 16:18:00 +01:00

src

storcon: use attached shard counts for initial shard placement (#8061)

2024-06-20 17:32:01 +01:00

Cargo.toml

storcon: add drain and fill background operations for graceful cluster restarts (#8014)

2024-06-19 11:55:30 +01:00