With capacity-aware balancing, if we're missing capacity for a normal node, we won't be able to proceed with tablet drain. Consider the following scenario: 1. Nodes: A, B 2. refresh stats with A and B 3. Add node C 4. Node B goes down 5. removenode B starts 6. stats refreshing fails because B is down If we don't have capacity stats for node C, load balancer cannot make decisions and removenode is blocked indefinitely. A reproducer is added in this patch. To alleviate that, we allow capacity stats to be collected for nodes which are reachable, we just don't update the table size part. To keep table stats monotonic, we cache previous results per node, so even if it's unreachable now, we use its last reported sizes. It's still more accurate than not refreshing stats at all. A node can be down for a long period, and other replicas can grow in size. It's not perfect, because the stale node can skew the stats in its direction, but ignoring it completely has its pitfalls too. Better solution is left for later.
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.