[RELEASE] ScyllaDB Enterprise 2022.1.8

The ScyllaDB team announces ScyllaDB Enterprise 2022.1.8, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2022.1.

Note that there is a newer Feature Enterprise release: ScyllaDB Enterprise 2022.2. While we will continue to support 2022.1 LTS, you can get additional features with 2022.2.

Related Links

Below is a list of performance and stability improvements and bug fixes, each with an open-source reference if available:

  • Stability: Range-scans have a protection against using the wrong service-level to continue a suspended range-scan. This protection had a mistake, resulting in the node crashing when the protection mechanism was triggered. multishard_mutation_query: reader_context::lookup_readers() is not exception safe w.r.t. closing readers #13784

  • Performance: ScyllaDB uses an interval map data structure from the Boost library to quickly locate sstables needed to service a read. Due to the way we interface with the library, updating the interval map was unnecessarily slow. This is now fixed. #11669

  • Stability: All rpc::client objects have to be stopped before they are destroyed. Currently this is done in
    messaging_service::shutdown(). The cql_test_env does not call shutdown() currently. This can lead to use-after-free, leading to sigsegv #12244

  • Stability: race condition in gossip and failure detector #10547

  • Stability: mutation_reader_merger can overflow stack when merging many empty readers. This may happen when running a second repair right after the other. #14415

  • UX: Allow tombstone GC in compaction to be disabled on user request #14077
    The fix adds new APIs /column_family/tombstone_gc and /storage_service/tombstone_gc, that will allow for disabling tombstone garbage collection (GC) in compaction.

    • Get status: curl -s -X GET ""
    • Enable GC: curl -s -X POST ""
    • Disable GC: curl -s -X DELETE ""

    The table name must be in keyspace:table format