The ScyllaDB team announces ScyllaDB Enterprise 2024.2.2, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2024.2 Feature (Short Term Support) Release.
2024.2.2 patch release includes multiple bug fixes.
Related Links
- Get ScyllaDB Enterprise 2024.2 (customers only, or 30-day evaluation)
- Upgrade Guide - ScyllaDB Enterprise 2024.1 to 2024.2
- Upgrade - ScyllaDB 6.0 to ScyllaDB Enterprise 2024.2
- Submit a ticket
The following issues are fixed in this release (with an open-source reference, if available):
CQL and correctness related
- CQL: CREATE TABLE with non-existing KS returns empty error#20097
Tablets
- Keyspaces with tablets enabled will now reject tables with counter columns, as counters aren’t yet supported with tablets. #19449
Stability
- Get_service_levels is an internal function that can be called by internal services, and directly by the user using LIST SERVICE LEVELS. The fix increases the timeout for the first (internal), where response time is less important. #20483
- Service level cache may not be populated at startup #21763
- Metrics created by
cql_sg_stats
need to be renamed when the corresponding scheduling group is renamed. This was causing a bug which resulted in double metrics, resulting in group0 applier fiber broke due to an exception. - service levels: silently fails when creating service level, using CQL CREATE SERVICE LEVEL, above scheduling groups limit.
- Stability: a rare SStable’s clustering key index lookup may yield incorrect position. This could happen in the event of LSA memory compaction in the middle of promoted index entry parsing which moves the cached page and the entry must span file pages, for index larger than 64KB. #20766
Performance
- types: large allocations and stalls while comparing Decimal values #21716
- The index page cache will now generate fewer disk IOPS if an index read is partially cached. #20935
- ScyllaDB tracks whether read requests are waiting for CPU or I/O. In one case, a disk read from the primary index was considered to be waiting on CPU, which reduced concurrency. This is now fixed. #21325