When testing mv admission control, we perform a large view update and check if the following view update can be admitted due to the high view backlog usage. We rely on a delay which keeps the backlog high for longer to make sure the backlog is still increased during the second write. However, in some test runs the delay is not long enough, causing the second write to miss the large backlog and not hit admission control. In this patch we keep the increased backlog high using another injection instead of relying on a delay to make absolute sure that the backlog is still high during the second write. Fixes scylladb/scylladb#20382 Closes scylladb/scylladb#20445
Scylla in-source tests.
For details on how to run the tests, see docs/dev/testing.md
Shared C++ utils, libraries are in lib/, for Python - pylib/
alternator - Python tests which connect to a single server and use the DynamoDB API unit, boost, raft - unit tests in C++ cql-pytest - Python tests which connect to a single server and use CQL topology* - tests that set up clusters and add/remove nodes cql - approval tests that use CQL and pre-recorded output rest_api - tests for Scylla REST API Port 9000 scylla-gdb - tests for scylla-gdb.py helper script nodetool - tests for C++ implementation of nodetool
If you can use an existing folder, consider adding your test to it. New folders should be used for new large categories/subsystems, or when the test environment is significantly different from some existing suite, e.g. you plan to start scylladb with different configuration, and you intend to add many tests and would like them to reuse an existing Scylla cluster (clusters can be reused for tests within the same folder).
To add a new folder, create a new directory, and then
copy & edit its suite.ini.