1ba995653e
Non system schema instantiation in `replica::distributed_loader::init_non_system_keyspaces` access tablets managed by group0, but a node may have crashed in the middle of raft command application and those tables may be inconsistent (there is no atomicity guaranty while a command is been applied. Fix that by moving existing group0 initialization before the call to `replica::distributed_loader::init_non_system_keyspaces`. The in memory state machine enablement stays in the same place since loading of a state machine into memory depends on schema already be instantiated into memory. No need to backport since this does not fix any known bug. In fact migration manager (the component that group0 state machine uses to manage schema tables) is careful to make sure all schema mutations are in the same commitlog segment, so they will be seen as applied atomically, but the bug may happen with dependencies between schema and other components managed by group0 like topology. Closes scylladb/scylladb#30207 * github.com:scylladb/scylladb: main: replay group0 raft log before loading non-system keyspaces raft: separate group0 server start from in-memory state machine enablement
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.