[RELEASE] ScyllaDB Enterprise 2023.1.7

The ScyllaDB team announces ScyllaDB Enterprise 2023.1.7, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2023.1 LTS Release.

2023.1.7 patch release includes multiple minor bug fixes.

ScyllaDB Enterprise’s latest Long Term Support (LTS) is 2024.1. While we continue to support 2023.1, you are encouraged to upgrade to it in coordination with the ScyllaDB Support team.

Related Links

The following issues are fixed in this release (with an open-source reference, if available):

  • Stability: frozen_mutation::unfreeze() stall in schema_tables.cc: calculate_schema_digest. The issue (stalls) manifest on cluster with a large schema #17841
  • Stability: a theoretical race when reading encryption_file_io_extension may lead to undefined behavior.
  • Stability: streaming might fail when a table is dropped. Streaming can be part of a repair, topology change (adding/removing a node), etc. #15370, #17028, #15598
  • Stability: nodetool removenode hangs in repair, waiting on streaming semaphore #17591
  • Stability: reader_permit::get_schema() is unsafe against table schema alter or drop #16180
  • Stability: Sporadic repair failure when adding a node #16821
  • Stability: a very rare use-after-free in sstables::key_view::explode() can be caused by a large enough partition key #17625
  • Stability: fair_queue: Do not pop unplugged class immediately. The issue can manifest with a crash during cleanup: [seastar/src/core/fair_queue.cc:222: void seastar::fair_queue::pop_priority_class seastar#eb093f8
  • Set up: iotune doesn’t close files that weren’t correctly opened, for example when test directory creation failed for whatever reason, leading to iotune crash. seastar#b9fd21d
  • Alternator: a bug in Alternator GSI updates of range key when using two new key columns in GSI #17119
  • Scylla AMI for EC2: Cannot get EC2 user data after enabled IMDSv2 scylla-machine-image#498