485df63fd5
Currently, the `system.compaction_history` table miss information like the type of compaction (cleanup, major, resharding, etc), the sstable generations involved (in and out), shard's id the compaction was triggered on and statistics on purged tombstones to be collected during compaction. The series extends the table with the following columns: - "compaction_type" (text) - "shard_id" (int) - "sstables_in" (list<sstableinfo_type>) - "sstables_out" (list<sstableinfo_type>) - "total_tombstone_purge_attempt" (long) - "total_tombstone_purge_failure_due_to_overlapping_with_memtable" (long) - "total_tombstone_purge_failure_due_to_overlapping_with_uncompacting_sstable" (long) with a user defined type `sstableinfo_type` that holds the information about sstable file - generation (uuid) - origin (text) - size (long) Additional statistics stored in the compaction_history have been incorporated in the API `/compaction_manager/compaction_history` and the `nodetool compactionhistory` command. No backport is required. It extends the existing compaction history output. Fixes https://github.com/scylladb/scylladb/issues/3791 Closes scylladb/scylladb#21288 * github.com:scylladb/scylladb: nodetool: Refactor of compactionhistory_operation nodetool: Add more stats into compactionhistory output api/compaction_manager: Extend compaction_history api compaction: Collect tombstone purge stats during compaction compacting_reader: Extend to accept tombstone purge statistics mutation_compactor: Collect tombstone purge attempts compaction_garbage_collector: Extend return type of max_purgeable_fn compaction: Extend compaction_result to collect more information system_keyspace: Upgrade compaction_history table system_keyspace: Create UDT: sstableinfo_type system_keyspace: Extract compaction_history struct system_keyspace: Squeeze update_compaction_history parameters compaction/compaction_manager: update_history accepts compaction_result as rvalue
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.