5bb1597a30
There are several transition stages that are executed by the topology coordinator with the help of barrier-and-drain raft commands. For the test to stop and remove a node while handling this stage it must inject a break-point into barrier handler, wait for it to happen and then stop the node without resuming the break-point. Then removenode from the cluster. The break-point suspends barrier handling when a specific tablet is in specific transition stage. Tablet ID and desired stage are configured via injector parameters. With today's error-injection facilities the way to suspend code execution is with injecting a lambda that waits for a message from the injection engine. Signed-off-by: Pavel Emelyanov <xemul@scylladb.com>
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.