ScyllaDB Enterprise 2021.1.5

The ScyllaDB team announces ScyllaDB Enterprise 2021.1.5, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2021.1. ScyllaDB Enterprise customers are encouraged to upgrade to ScyllaDB Enterprise 2021.1.5 in coordination with the ScyllaDB support team.

ScyllaDB Enterprise 2021.1.5 brings improvement to ScyllaDB Images for public cloud, Cloud Formation enhancements and other improvements and bug fixes (below)

ScyllaDB Enterprise Image

(based on Ubuntu 20.04)

• disables default upgrades
• Improves start time by moving 3rd party packages installation from the start up time, to image creation time.

Cloud Formation for ScyllaDB Enterprise

• A new variable “VpcCidrIp”, allowing you to Set CIDR IP range for VPC. Previously, the range was hard coded to 172.31.0.0/16 (open source reference #157)
• Cloud Formation template was reordered for better readability (open source reference #180)

Related Links

• Get ScyllaDB Enterprise 2021.1.5 (customers only, or 30-day evaluation)
• Upgrade from 2020.1.x to 2021.1.y
• Upgrade from ScyllaDB Open Source 4.3 to ScyllaDB Enterprise 2021.1
• Submit a ticket

A list of stability improvements and bug fixes below, each with open source reference, is available:

• Stability: gnutls 3.6.x causes the unwinder to crash when collecting a backtrace. This can crash a node when the stall detector detects a stall, and that stall happens to be in gnutls. Fix by pulling in gnutls 3.7.2 from Fedora 34.
• Monitoring: storage_proxy counters are not updated on cql counter operations #4337
• Performance: read latency increase after deletion of high percentage of the data, as many rows covered by a single range tombstone, which go through row cache are very slow #8626
• CQL: Disable Encryption at Rest on table does not work (see #8773)
• Stability: ScyllaDB aborts with error “./seastar/src/core/fstream.cc:172: virtual seastar::file_data_source_impl::~file_data_source_impl(): Assertion `_reads_in_progress == 0' failed” when sstable mutation reader is fast forwarding #9049
• CQL: Creating a table that looks like a secondary index breaks the secondary index creation mechanism #8620. This fix accidentally broke CREATE INDEX IF NOT EXISTS #8717
• CQL: Fix index name conflicts with regular tables. When an index is created without an explicit name, a default name is chosen. However, there was no check if a table with a conflicting name already exists.  #8632
• Stability: excessive compaction of a fully expired TWCS table when running repair #8710
• Stability: evictable_reader: self validation triggers when a partition disappears after eviction #8893
• Stability: evictable_reader: _drop_static_row can drop of the static row from an unintended partition #8923
• Stability: ScyllaDB aborts with error “./seastar/src/core/fstream.cc:172: virtual seastar::file_data_source_impl::~file_data_source_impl(): Assertion `_reads_in_progress == 0' failed” when sstable mutation reader is fast forwarding #9049
• Monitoring: API uses incorrect plus<int> to sum up cf.active_memtable().partition_count(), which can result with  the value wrapped around if bigger than 232, and return the wrong metric.  #9090
• Upscale (adding cores): On some environments /sys/devices/system/cpu/cpufreq/policy0/scaling_governor does not exist even if it supported CPU scaling. Instead, /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is used.  #9191

25 Aug 2021