The ScyllaDB team announces ScyllaDB Enterprise 2022.1.5, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2022.1.
Related Links
- Get ScyllaDB Enterprise 2022.1.5 (customers only, or 30-day evaluation)
- Upgrade from 2021.1.x to 2022.1.y
- Upgrade from ScyllaDB Open Source 5.0 to ScyllaDB 2022.1
- Submit a ticket
Below is a list of performance and stability improvements and bug fixes, each with an open-source reference if available:
- CQL: Different token calculation functions for “empty” partition keys cause sstable reader to misuse index #9352
- CQL: Empty strings are now allowed in materialized view partition keys. #9352
- CQL: Wrong validation of blobs in INSERT JSON #10114
- CQL, batch statements, inserting a row with a null key column should be forbidden #12060
- Stability: [index cache] Multiple 800ms+ reactor stalls during nodetool cleanup (with index cache disabled) due to the local index cache not being evicted gently when _upper_bound existed. #12271
- Stability: A crash in Scylla memory management code, triggered by index file caching, was fixed. The bug was caused by an allocation from within the memory allocator, causing cache eviction to free memory. Freeing the evicted items re-enters the memory allocator in a way that was not expected by the code. Fixes #9573
- Config: Before this release, updating static shares configuration parameters, compaction_static_shares and memtable_flush_static_shares required a restart to apply. These updated parameters apply immediately now.
- Init: scylla_setup “provisioning in a similar environment” message is missing a value for --online-discard parameter #11700
- Init: scylla-server fails to start on n2-highmem-16 (6000 GB) instance. Fixed by removing diskCount vs cpu restrictions.