ScyllaDB Enterprise 2021.1.15

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

Note that ScyllaDB Enterprise 2022.1 LTS is the latest stable branch and you are encouraged to upgrade in coordination with the ScyllaDB support team.

ScyllaDB Enterprise 2021.1.15 brings focus on bug fixes and stabilization.

Related Links

Below is a list of performance and stability improvements and bug fixes, each with an open source reference:

  • Stability: replica, evict all inactive reads for a table when dropping it #11264
  • Stability: Make cleanup withstand a better disk pressure scenario, for example, when running cleanup in an entire keyspace with low available storage. Cleanup will now start with smaller tables first, so bigger tables will have more space available once they’re reached to satisfy their space requirement.
  • Speculative retry will no longer consider failed responses when calculating the 99th percentile of a request.
  • Considering them leads to the latency threshold being continuously raised since failed (timed out) requests have very long latency, so the effectiveness of the feature is much reduced. Now it will only consider successful responses. #3746 #7342
  • Stability: Query with multiple indexes, one date, one boolean, fail with ServerError #7659
  • Stability: A problem with COMPACT STORAGE tables representation in Change Data Capture has been corrected. #8410
  • Stability: A SELECT statement could result in unbounded concurrency (leading to an out-of-memory error) in some circumstances; this is now fixed. #8799
  • Tools: nodetool checkAndRepairCdcStreams shouldn’t fail when there are nodes in LEFT state #9771
  • UX: Failure to apply a failed batchlog is silent #10636
  • Stability: 2 Nodes failed after bloom_filter_fp_chance was modified to an unreasonable low number #11524

12 Oct 2022