eb7be9010d
We switched to the size-based load balancing, which now has more strict requirements for load stats. We no longer need only per-node stats, but also per-tablet stats. Bootstrapping a node triggers stats refresh, but allocating tablets on table creation didn't. So after creating a table, load balancer couldn't make progress for up to 60s (stats refresh period). This makes tests take longer, and can even cause failures if tests are using a low-enough timeout. Fixes https://github.com/scylladb/scylladb/issues/27921 No backport becuse only master is vulnerable (size-based load balancing). Closes scylladb/scylladb#27926 * https://github.com/scylladb/scylladb: test: cluster: Add reproducer for missed notification in topology coordinator topology_coordinator: Wake up the state machine after stats refresh topology_coordinator: Move tablet_load_stats_refresh_before_rebalancing injection earlier topology_coordinator: Fix potential missed notification topology_coordinator: Refresh load stats after table is created or altered tablets: Do a group0 read barrier on tablet load stats refresh topology_coordinator: Ensure stats are refreshed in the gossip scheduling group test: Use ManagerClient.{disable,enable}_tablet_balancing() test: Add missing calls to disable_tablet_balancing() in tests which use move_tablet() API test: pylib: Introduce ManagerClient.{disable,enable}_tablet_balancing()
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.