[RELEASE] ScyllaDB Enterprise 2022.1.6

Release Notes
, ,
1

The ScyllaDB team announces ScyllaDB Enterprise 2022.1.6, 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:

  • CQL: Deleting a long base partition may leave some undeleted materialized view rows #12297

  • CQL: USING TIMESTAMP allows setting the mutation timestamp on a CQL statement level. It has a sanity check that prevents setting timestamps in the future, as these can be hard to delete, but sometimes one wishes to do so anyway. There is now a configuration option that allows disabling the feature. #12527

  • CQL: scylla: types: is_tuple(): doesn’t handle reverse types. For example, a schema with reversed clustering key component; this component will be incorrectly represented in the schema CQL dump: the UDT will lose the frozen attribute. When attempting to recreate this schema based on the dump, it will fail as the only frozen UDTs are allowed in primary key components. #12576

  • Alternator Streaming API: unexpected ARN values by list streams paged responses. This issue may only affect users with many, more than 100, tables with streams #12601

  • Stability: Gossip now uses a better source to get live node information for truncate, reducing false failures of the TRUNCATE operation. #10296, #11928

  • Stability: Cached reads may temporarily miss rows under rare conditions #12451

  • Stability: Crash when reporting error on invalid CQL query involving field selection from a user-defined type #12739

  • Stability: reader_concurrency_semaphore: inactive readers are only evicted on the admission path #11770

  • Stability: During rebuild on asymmetric cluster several aborts and coredump happened #11923 (introduced by the fix for #11770 above)

  • Stability: Memtable(s) are not flushed when cleaning up a table, leaving disowned tokens in the memtable, which might be resurrected.#1239

  • Stability: Enabling table encryption (see Encryption at Rest) aborts Scylla when key_provider is not specified.

  • Stability: error “reader_concurrency_semaphore - Semaphore sl:oltp_read_concurrency_sem with 0/100 count and -74538773/0 memory resources”. Root cause is reader_concurrency_semaphore_group partitioning memory is broken. In some cases, this bug may, after a few cycles of updates, lead to semaphore without any memory units unable to admit any reads. In turn this may lead to high latency and even denial of service.

  • Stability: Nodes SegFaulted in short succession after restore. The root cause was that the Workload Prioritization scheduling group was not robust enough.

  • Stability: ScyllaDB tracks transient memory used by queries. However, it did not track decompressed memory buffers, which could lead to running out of memory in some complicated queries. #12448

  • Stability: crash in Materialized View update row locking, caused by a race condition #12632

  • Stability: preemption pitfall around waiting for readmission (found is fuzzy tests) #10187

  • Stability: error “reader_concurrency_semaphore - Semaphore sl:oltp_read_concurrency_sem with 0/100 count and -74538773/0 memory resources”. Root cause is reader_concurrency_semaphore_group partitioning memory is broken. In some cases, this bug may, after a few cycles of updates, lead to semaphore without any memory units unable to admit any reads. In turn this may lead to high latency and even denial of service.

  • Performance: parsers are compiled without inlining, even in release mode #12463