Joonas Koivunen 730db859c7 feat(timeline_detach_ancestor): success idempotency (#8354) ...

Right now timeline detach ancestor reports an error (409, "no ancestor")
on a new attempt after successful completion. This makes it troublesome
for storage controller retries. Fix it to respond with `200 OK` as if
the operation had just completed quickly.

Additionally, the returned timeline identifiers in the 200 OK response
are now ordered so that responses between different nodes for error
comparison are done by the storage controller added in #8353.

Design-wise, this PR introduces a new strategy for accessing the latest
uploaded IndexPart:
`RemoteTimelineClient::initialized_upload_queue(&self) ->
Result<UploadQueueAccessor<'_>, NotInitialized>`. It should be a more
scalable way to query the latest uploaded `IndexPart` than to add a
query method for each question directly on `RemoteTimelineClient`.

GC blocking will need to be introduced to make the operation fully
idempotent. However, it is idempotent for the cases demonstrated by
tests.

Cc: #6994

2024-07-15 17:47:53 +00:00

..

migrations

Clean up 'attachment service' names to storage controller (#7326)

2024-04-05 16:18:00 +01:00

src

feat(timeline_detach_ancestor): success idempotency (#8354)

2024-07-15 17:47:53 +00:00

Cargo.toml

storcon: add drain and fill background operations for graceful cluster restarts (#8014)

2024-06-19 11:55:30 +01:00