dcaf6582c4
The test does the following: - Enables an error injection which will cause further view updates to get stuck, occupying space in memory and affecting the backlog, - Performs a single, large write to the base table which causes a single view update to be generated; the write is then followed with one more, small write to make sure that the other write will be affected by the first write's backlog, - Reads relevant metrics in order to check the exact value of the delay that was calculated for the base table write due to MV backpressure. This is done for different values of the MV delay configuration parameter (view_flow_control_delay_limit_in_ms) and the calculated delays are collected into a list. Lastly, the test checks that the relation between parameter value and the calculated delays is linear.
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++ cqlpy - 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.