Vlad Lazar 1c96957e85 storcon: run db migrations after step down sequence (#8756) ...

## Problem

Previously, we would run db migrations before doing the step-down
sequence. This meant that the current leader would have to deal with
the schema changes and that's generally not safe.

## Summary of changes

Push the step-down procedure earlier in start-up and
do db migrations right after it (but before we load-up the in-memory
state from the db).

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

2024-08-20 14:00:36 +01:00

..

client

storage scrubber: GC ancestor shard layers (#8196)

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

migrations

storcon: implement graceful leadership transfer (#8588)

2024-08-12 13:58:46 +01:00

src

storcon: run db migrations after step down sequence (#8756)

2024-08-20 14:00:36 +01:00

Cargo.toml

storage_controller: start adding chaos hooks (#7946)

2024-08-02 09:37:44 +01:00