740b240e9d
The test only looked at the initial cdc_generation generation. It made the changes bigger to go past the raft max_command_size limit. It then made sure this large mutation set is saved in several raft commands. In this commit we enhance the test to check that the mutations are properly handled during snapshot transfer. The problem is that the entire system.cdc_generations_v3 table is read into the topology_snapshot and it's total size can exceed the commitlog max_record_size limit. We need a separate injection since the compaction could nullify the effects of the previous injection. The test fails without the fix from the previous commit.
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.