[RELEASE] ScyllaDB Enterprise 2022.1.7

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

  • Stability: storage_service::removenode should not silence exceptions #11722
  • Stability: a rare issue when updating the schema more than once in once per millisecond #13594
  • Stability: a rare crash due to null pointer dereference: clear_gently of disengaged unique_ptr dereferences nullptr #13636
  • Stability: distributed_loader should first detect the highest generation in a table before allowing new sstables to be created in it #11793. This is a root cause for: View building fail to move staging SSTables to base dir because generations are taken #11789
  • Packaging: RPM package dependencies issue. When installing a specific version with yum/dnf, scylla-python3 version will not match the specified version, but the latest one. #13222
  • Stability: bad_alloc (seastar - Failed to allocate 536870912 bytes) #13491. Root cause is a logic fault causing the reader to attempt to read all the data, consuming all memory. Can occur during sstableloader/nodetool refresh, repair or range scan.