46a712d6d4
To find the raft group leader of a group, a node must be a member of this group. In a few test cases in test_strong_consistency.py we try to get the leader info without knowing raft group members, so we may initially fail and we retry on another node. This is inefficient - trying to get the leader from a non-member ends in a timeout for the leader check, so the test case takes an additional 60s. In this patch we avoid this by checking raft group members (i.e. tablet replicas) before trying to get the leader, and then only get the leader from one of the replicas. On average, this should speed up the test_strong_consistency.py by 85s. Fixes: SCYLLADB-2266 Fixes: SCYLLADB-2268 Closes scylladb/scylladb#30165
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.