mirror of
https://github.com/scylladb/scylladb.git
synced 2026-06-07 07:23:15 +00:00
ef97adc72a
" We have recently seen out-of-order partitions getting into sstables causing major disruption later on. Given the damage caused, it was again raised that we should enable partition key monotonicity validation unconditionally in the sstable write path. This was also raised in the past but dismissed as key validation was suspected (but not measured) to add considerable per-fragment overhead. One of the problems was that the key monotonicity validation was all or nothing. It either validated all (clustering and partition) key monotonicity or none of it. This series takes a second look at this and solves the all-or-nothing problem by making the configuration of the key monotonicity check more fine grained, allowing for enabling just token monotonicity validation separately, then enables it unconditionally. Refs: #7623 Tests: unit(release) " * 'sstable-writer-validate-partition-keys-unconditionally/v3' of https://github.com/denesb/scylla: sstables: enable token monotonicity validation by default mutation_fragment_stream_validator: add token validation level mutation_fragment_stream_validating_filter: make validation levels more fine-grained