88ab8db944
View building is an expensive process that takes a long time to complete. During the build, it's impact on other work should be minimized, even at the expense of slightly slowing it down. Instead, view building is currently performed in the the same scheduling group (gossip) as other high-priority tasks, in particular raft processing, which slows it down, making races more likely and increasing the number of retries that need to be done. While view building is still initiated in the gossip group (as it's the result of adding a view, which is a schema change), in this patch the bulk of the view building work is moved to a low-priority, maintenance scheduling group (named "streaming" after its main use case). Additionally, a test is added, where we make sure that the scheduling group is the one most used when building a view. Fixes https://github.com/scylladb/scylladb/issues/21232 Closes scylladb/scylladb#21326
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.