Files
scylladb/idl
Petr Gusev 46f73fcaa6 storage_proxy: add fencing for mutation
At the call site, we use the version, captured
in erm/token_metadata. In the handler, we use
double checking, apply_fence after the local
write guarantees that no mutations
succeed on coordinators if the fence version
has been updated on the replica during the write.

Fencing was also added to mutate_locally calls
on request coordinator, for the case
if this coordinator was isolated from the
topology change coordinator and missed the
barrier_and_drain command.
2023-06-15 15:52:49 +04:00
..
2023-04-23 08:37:32 +03:00
2023-02-14 11:19:03 +02:00
2023-05-30 13:14:19 +04:00
2023-04-23 08:37:32 +03:00
2023-03-01 10:25:25 +02:00