[RELEASE] ScyllaDB Enterprise 2022.2.7

Release Notes
, ,
1

The ScyllaDB team announces ScyllaDB Enterprise 2022.2.7, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2022.2.

Related Links

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

  • CQL: TTL unexpected behavior when setting to 0 on a table with default_time_to_live #6447
  • Monitoring: new metric for CQL request and response sizes #13061
  • Stability: heavy stalls coming from a memory reclaimer (compression related) customer. Root cause is too frequent clear of reusable compression buffers.
  • Stability: reactor stalls in commitlog replay path due to commit log regexp processing #11710
  • Stability: storage_service::removenode should not silence exceptions #11722
  • Stability: a rare crash due to null pointer dereference: clear_gently of disengaged unique_ptr dereferences nullptr #13636
  • Stability: db/view: update view generator doesn’t close staging sstable reader on exceptions #13413
  • Stability: direct_failure_detector::ping_with_timeout() causes exceptions to be thrown every 100ms times the number of live nodes, which spam the logs, and might slow it down #13278
  • Stability: A Seastar update fixed an ambiguity in the http parser, which caused Alternator requests to be unnecessarily slow. 12468
  • Stability:: Internal error in a COUNT request with empty IN. The query “select count(*) from {table1} where p in ()” should result in the count 0, because the empty p in () matches no row. However, what we get in Scylla now is an internal error. #12475
  • Stability: on_internal_error doesn’t log an error when not aborting #13786
  • 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.