John Spray 68d8acfd05 storage controller: don't hold detached tenants in memory (#10264) ...

## Problem

Typical deployments of neon have some tenants that stay in use
continuously, and a background churning population of tenants that are
created and then fall idle, and are configured to Detached state.
Currently, this churn of short lived tenants results in an
ever-increasing memory footprint.

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

## Summary of changes

- At startup, filter to only load shards that don't have Detached policy
- In process_result, check if a tenant's shards are all Detached and
observed=={}, and if so drop them from memory
- In tenant_location_conf and other tenant mutators, load the tenants'
shards on-demand if they are not present

2025-01-08 18:12:09 +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

storage controller: don't hold detached tenants in memory (#10264)

2025-01-08 18:12:09 +00:00

Cargo.toml

cargo: update diesel, pq-sys (#10256)

2025-01-03 10:20:18 +00:00