478b8f09df
In case of decommission, it's not desirable because it's less urgent. In case of removenode, it leads to failure of removenode operation because scheduled co-locating migration will fail if the destination is on the excluded node, and this failure will be interpreted as drain failure and coordinator will cancel the request. Not a problem before "parallel decommission" because this failure is only a streaming failure, not a barrier failure, so exception doesn't escape into the catch clause in transition stage handler, and the migration is simply rolled back. Once draining happens in the tablet migration track, streaming failure will be interpreted as drain failure and cancel the request.
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.