bf47de9f7f
Building upon commit69b47694, this change addresses a subtle synchronization weakness in node visibility checks during recovery mode testing. Previous Approach: - Waited only for the first node to see its peers - Insufficient to guarantee full cluster consistency Current Solution: 1. Implement comprehensive node visibility verification 2. Ensure all nodes mutually recognize each other 3. Prevent potential schema propagation race conditions Key Improvements: - Robust cluster state validation before keyspace creation - Eliminate partial visibility scenarios Fixes scylladb/scylladb#21724 Signed-off-by: Kefu Chai <kefu.chai@scylladb.com> Closes scylladb/scylladb#21726 (cherry picked from commit65949ce607) Closes scylladb/scylladb#21734
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.