Vlad Lazar ae527ef088 storcon: implement graceful leadership transfer (#8588) ...

## Problem
Storage controller restarts cause temporary unavailability from the
control plane POV. See RFC for more details.

## Summary of changes
* A couple of small refactors of the storage controller start-up
sequence to make extending it easier.
* A leader table is added to track the storage controller instance
that's currently the leader (if any)
* A peer client is added such that storage controllers can send
`step_down` requests to each other (implemented in
https://github.com/neondatabase/neon/pull/8512).
* Implement the leader cut-over as described in the RFC
* Add `start-as-candidate` flag to the storage controller to gate the
rolling restart behaviour. When the flag is `false` (the default), the
only change from the current start-up sequence is persisting the leader
entry to the database.

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

..

down.sql

storcon: implement graceful leadership transfer (#8588)

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

up.sql

storcon: implement graceful leadership transfer (#8588)

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