John Spray 256058f2ab pageserver: only write out legacy tenant config if no generation (#6891) ...

## Problem

Previously we always wrote out both legacy and modern tenant config
files. The legacy write enabled rollbacks, but we are long past the
point where that is needed.

We still need the legacy format for situations where someone is running
tenants without generations (that will be yanked as well eventually),
but we can avoid writing it out at all if we do have a generation number
set. We implicitly also avoid writing the legacy config if our mode is
Secondary (secondary mode is newer than generations).

## Summary of changes

- Make writing legacy tenant config conditional on there being no
generation number set.

2024-02-26 10:24:58 +00:00

..

benches

bench_walredo: use tokio multi-threaded runtime (#6743)

2024-02-16 16:31:54 +01:00

client

Implement a sharded time travel recovery endpoint (#6821)

2024-02-21 16:35:37 +01:00

ctl

live-reconfigurable virtual_file::IoEngine (#6552)

2024-02-07 17:47:55 +00:00

pagebench

per-TenantShard read throttling (#6706)

2024-02-16 21:26:59 +01:00

src

pageserver: only write out legacy tenant config if no generation (#6891)

2024-02-26 10:24:58 +00:00

test_data

Add walingest test (#5892)

2023-11-28 12:50:53 -05:00

Cargo.toml

per-TenantShard read throttling (#6706)

2024-02-16 21:26:59 +01:00