mirror of
https://github.com/scylladb/scylladb.git
synced 2026-04-21 09:00:35 +00:00
c04007c755
This is a follow-up of the previous fix: https://github.com/scylladb/scylladb/pull/26030
The test test_user_writes_rejection starts a 3-node cluster and
creates a large file on one of the nodes, to trigger the out-of-space
prevention mechanism, which should reject writes on that node.
It waits for the log message 'Setting critical disk utilization mode: true'
and then executes a write expecting the node to reject it.
Currently, the message is logged before the `_critical_disk_utilization`
variable is actually updated. This causes the test to fail sporadically
if it runs quickly enough.
The fix splits the logging into two steps:
1. "Asked to set critical disk utilization mode" - logged before any action
2) "Set critical disk utilization mode" - logged after `_critical_disk_utilization` has been updated
The tests are updated to wait for the second message.
Fixes https://github.com/scylladb/scylladb/issues/26004
Closes scylladb/scylladb#26392
(cherry picked from commit 7ec369b900)
Closes scylladb/scylladb#26626
Extension of the cluster tests, where all tests require externally mounted volumes to be used by scylla cluster nodes. The volumes are passed with --workdir.
The volumes can be of any size. A help generator space_limited_servers is provided
to easily create a cluster of any given number of nodes, where each node operates in
a separate volume.