Do not hold erm during repair of a tablet that is started with tablet repair scheduler. This way two different tablets can be repaired and migrated concurrently. The same tablet won't be migrated while being repaired as it is provided by topology coordinator. Use topology_guard to maintain safety. Fixes: https://github.com/scylladb/scylladb/issues/22408. Needs backport to 2025.1 that introduces the tablet repair scheduler. Closes scylladb/scylladb#23362 * github.com:scylladb/scylladb: test: add test to check concurrent tablets migration and repair repair: do not hold erm for repair scheduled by scheduler repair: get total rf based on current erm repair: make shard_repair_task_impl::erm private repair: do not pass erm to put_row_diff_with_rpc_stream when unnecessary repair: do not pass erm to flush_rows_in_working_row_buf when unnecessary repair: pass session_id to repair_writer_impl::create_writer repair: keep materialized topology guard in shard_repair_task_impl repair: pass session_id to repair_meta
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.