13fc2bd854
The series adds a step during node's boot process, just before completing the initialization, in which the node sends a notification to all other normal nodes in the cluster that it is UP now. Other nodes wait for this node to be UP and in normal state before replying. This ensures that, in a healthy cluster, when a node start serving queries the entire cluster knows its up-to-date state. The notification is a best effort though. If some nodes are down or do not reply in time the boot process continues. It is somewhat similar to shutdown notification in this regard. * 'gleb/notify-up-v2' of github.com:scylladb/scylla-dev: gossiper: wait for a bootstrapping node to be seen as normal on all nodes before completing initialization Wait for booting node to be marked UP before complete booting. gossiper: move gossip verbs to the idl
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.