Dmitrii Kovalkov 133f16e9b5 storcon: finish safekeeper migration gracefully (#12528) ...

## Problem
We don't detect if safekeeper migration fails after the the commiting
the membership configuration to the database. As a result, we might
leave stale timelines on excluded safekeepers and do not notify
cplane/safekepeers about new configuration.

- Implements solution proposed in
https://github.com/neondatabase/neon/pull/12432
- Closes: https://github.com/neondatabase/neon/issues/12192
- Closes: [LKB-944](https://databricks.atlassian.net/browse/LKB-944)

## Summary of changes
- Add `sk_set_notified_generation` column to `timelines` database
- Update `*_notified_generation` in database during the finish state.
- Commit reconciliation requests to database atomically with membership
configuration.
- Reload pending ops and retry "finish" step if we detect
`*_notified_generation` mismatch.
- Add failpoints and test that we handle failures well

2025-07-22 14:58:20 +00:00

..

client

storcon + safekeeper + scrubber: propagate root CA certs everywhere (#11418)

2025-04-04 06:30:48 +00:00

migrations

storcon: finish safekeeper migration gracefully (#12528)

2025-07-22 14:58:20 +00:00

src

storcon: finish safekeeper migration gracefully (#12528)

2025-07-22 14:58:20 +00:00

Cargo.toml

A few SC changes (#12615)

2025-07-17 13:14:36 +00:00