The ScyllaDB team announces ScyllaDB Enterprise 2022.2.8, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2022.2.
Related Links
- Get ScyllaDB Enterprise 2022.2.8 (customers only, or 30-day evaluation)
- Upgrade from 2022.1.x to 2022.2.y
- Upgrade from ScyllaDB Open Source 5.1 to ScyllaDB 2022.2
- Submit a ticket
The following issues are fixed in this release (with an open-source reference, if available):
- Alternator: Scylla Enterprise 2022.2.0 prompts Alternator TTL to production. It was not enabled by default. Now it is. #12037.
- Setup: fix a regression in setup, which overrides the manual update of perftune.yaml #11385 #10121
- Setup: updates in perftune.py, improving performance for larger servers (32 cores and above)
- introduce a generic auto_detect_irq_mask(cpu_mask) function
- auto-select the same number of IRQ cores on each NUMA
- Stability: ALTER KEYSPACE can break tables with UDT columns #14139 (introduced in 2022.2)
- Stability: Crash on compaction completion when staging directory is reshaped and ICS ends up with a run containing staging and non-staging files.
- Stability: Shutting down auth service may hang #13545
- Stability: ‘sleep_aborted’ error during Scylla shutdown #13374
- Stability: possible use-after-move in virtual table for secondary indexes #13396
- Stability: possible use-after-move when initializing row cache with dummy entry #13400
- Stability: possible use-after-move in virtual table for secondary indexes #13396
- Stability: possible use-after-move when making streaming reader #13397
- Stability: possible use-after-move when reading from SSTable in reverse #13394
- Stability: possible use-after-move when tracking view builder progress #13395
- Performance: Compaction manager “periodic reevaluation” is one-off. This means that compaction was not kicking in later for a table, with low to none write activity, that had expired data 1 hour from now. #13430
- Performance: Compaction manager can cause reactor stalls during periodic submission #12390
- 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
- Performance: SSTable set is left uncompacted post off-strategy compaction completion, which may lead to suboptimal read and space amplification until the next compaction #13429
- UX: non informative iotune warnings in scylla_kernel_check #13373