eefb6a0642
The previous implementation did not handle topology changes well: * In `node_local_only` mode with CL=1, if the current node is pending, the CL is increased to 2, causing `unavailable_exception`. * If the current tablet is in `write_both_read_old` and we try to read with `node_local_only` on the new node, the replica list will be empty. This patch changes `node_local_only` mode to always use `my_host_id` as the replica list. An explicit check ensures the current node is a replica for the operation; otherwise `on_internal_error` is called. backport: not needed, since `node_local_only` is only used in LWT for tablets and it hasn't been released yet. Closes scylladb/scylladb#25508 * github.com:scylladb/scylladb: test_tablets_lwt: add test_lwt_during_migration storage_proxy: node_local_only: always use my_host_id
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.