John Spray d182ff294c storcon: respect tenant scheduling policy in drain/fill (#9657) ...

## Problem

Pinning a tenant by setting Pause scheduling policy doesn't work because
drain/fill code moves the tenant around during deploys.

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

## Summary of changes

- In drain, only move a tenant if it is in Active or Essential mode
- In fill, only move a tenant if it is in Active mode.

The asymmetry is a bit annoying, but it faithfully respects the purposes
of the modes: Essential is meant to endeavor to keep the tenant
available, which means it needs to be drained but doesn't need to be
migrated during fills.

2024-11-06 15:14:43 +00:00

..

client

Remove unnecessary dependencies (#9000)

2024-09-17 17:55:45 +03:00

migrations

storcon: track preferred AZ for each tenant shard (#8937)

2024-09-06 13:11:17 +01:00

src

storcon: respect tenant scheduling policy in drain/fill (#9657)

2024-11-06 15:14:43 +00:00

Cargo.toml

Rename hyper 1.0 to hyper and hyper 0.14 to hyper0 (#9254)

2024-10-03 16:33:43 +02:00