273f664496
With the introduction of colocated tables, all the tablet transitions now operate on groups of colocated tablets instead of individual tablets. such is tablet migration, and also tablet repair. The tablet repair currently doesn't work on individual tablets due to the limitations in the tablet map being shared. The way it was implemented to work on a group of colocated tablets is by repairing all the colocated tablets together, using a dedicated rpc, and setting a shared repair_time in the shared tablet map. It was implemented this way because we wanted to have some way to repair the tablets of a colocated table. However, we want to change this in the next release so that it will be possible to repair the tablets of a colocated table individually. In order to simplify and prepare for the future change, we prefer until then to not repair colocated tables at all. otherwise, we will need to support both the shared repair and individual repair together for a long time, and the upgrade will be more complicated. We change the handling of the tablet 'repair' transition to repair only the base table's tablets. It means it will not be possible to request tablet repair for a non-base colocated table such as local MV, CDC and paxos table. This restriction will be temporary until a later release where we will suuport repairing colocated tablets. This is a reasonable restriction because repair for these kind of tables is not required or as important as for normal tables. Fixes scylladb/scylladb#27119
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.