Łukasz Paszkowski 4657d9e32c streaming: reject mutation fragments on critical disk utilization ...

The stream_mutation_fragments RPC handler did not check
is_in_critical_disk_utilization_mode before accepting incoming mutation
fragments. This meant load-and-stream (nodetool refresh --load-and-stream)
could push data onto a node at critical disk utilization, potentially
filling the disk completely.

Add a critical disk utilization check in the get_next_mutation_fragment
lambda, throwing critical_disk_utilization_exception when the node is in
critical mode. This mirrors the existing protection in stream_blob.cc.

Also remove the xfail marker from the corresponding test added in the
previous commit.

2026-04-17 09:31:26 +02:00

32 KiB

Raw Blame History

View Raw