Vlad Lazar 3977e0a7a3 storcon: shutdown with clean observed state (#8494) ...

## Problem
Storcon shutdown did not produce a clean observed state. This is not a
problem at the moment, but we will need to stop all reconciles with
clean observed state for rolling restarts.

I tried to test this by collecting the observed state during shutdown
and comparing it with the in-memory observed
state, but it doesn't work because a lot of tests use the cursed attach
hook to create tenants directly through the ps.

## Summary of Changes
Rework storcon shutdown as follows:
* Reconcilers get a separate cancellation token which is a child token
of the global `Service::cancel`.
* Reconcilers get a separate gate
* Add a mechanism to drain the reconciler result queue before
* Put all of this together into a clean shutdown sequence

Related https://github.com/neondatabase/cloud/issues/14701

2024-07-25 15:13:34 +01:00

..

client

storage scrubber: GC ancestor shard layers (#8196)

2024-07-19 19:07:59 +03:00

migrations

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

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

src

storcon: shutdown with clean observed state (#8494)

2024-07-25 15:13:34 +01:00

Cargo.toml

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

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