Arpad Müller 4de2f0f3e0 Implement a sharded time travel recovery endpoint (#6821) ...

The sharding service didn't have support for S3 disaster recovery.

This PR adds a new endpoint to the attachment service, which is slightly
different from the endpoint on the pageserver, in that it takes the
shard count history of the tenant as json parameters: we need to do
time travel recovery for both the shard count at the target time and the
shard count at the current moment in time, as well as the past shard
counts that either still reference.

Fixes #6604, part of https://github.com/neondatabase/cloud/issues/8233

---------

Co-authored-by: John Spray <john@neon.tech>

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

..

attachment_service

Implement a sharded time travel recovery endpoint (#6821)

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

src

Implement a sharded time travel recovery endpoint (#6821)

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

.gitignore

Revert "Use actual temporary dir for pageserver unit tests"

2023-01-19 20:16:56 +01:00

Cargo.toml

control_plane: follow up for embedded migrations (#6647)

2024-02-09 14:26:50 +00:00

safekeepers.conf

Separate mgmt and libpq authentication configs in pageserver. (#3773)

2023-03-15 13:52:29 +02:00

simple.conf

tests: enable multiple pageservers in neon_local and neon_fixture (#5231)

2023-09-08 16:19:57 +01:00