John Spray af99c959ef storage controller: use SERIALIZABLE isolation level (#7792) ...

## Problem

The storage controller generally assumes that things like updating
generation numbers are atomic: it should use a strict isolation level.

## Summary of changes

- Wrap all database operations in a SERIALIZABLE transaction.
- Retry serialization failures, as these do not indicate problems and
are normal when plenty of concurrent work is happening.

Using this isolation level for all reads is overkill, but much simpler
than reasoning about it on a per-operation basis, and does not hurt
performance.

Tested this with a modified version of storage_controller_many_tenants
test with 128k shards, to check that our performance is still fine: it
is.

2024-05-17 16:44:33 +01:00

..

migrations

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

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

src

storage controller: use SERIALIZABLE isolation level (#7792)

2024-05-17 16:44:33 +01:00

Cargo.toml

Store operation identifier in IdLockMap on exclusive lock (#7397)

2024-05-03 09:38:19 +01:00