The ScyllaDB team announces Scylla Enterprise 2020.1.11, a bug-fix production-ready Scylla Enterprise patch release for Scylla Enterprise 2020.1.
Note that the latest stable version of Scylla Enterprise is 2021.1 and users are encouraged to upgrade to it.
As always, Scylla Enterprise customers are encouraged to upgrade in coordination with the Scylla support team.
See the list of stability improvements and bug fixes below.
- Get Scylla 2020.1.11 (customers only, or 30-day evaluation)
- Upgrade from 2019.1.x to 2020.1
- Upgrade from 2019.1.x to 2019.1.y
- Upgrade from Scylla Open Source 4.0 to Scylla 2020.1
- Submit a ticket
Fixed issues in this release are listed below, with open source references, if present:
- Stability: abort streaming of data which is triggered by removenode operation if that node is already forcefully removed #8651
- CQL: Disable Encryption at Rest on table does not work (see #8773)
- 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
- 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_governordoes not exist even if it supported CPU scaling. Instead,
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governoris used. #9191
01 Sep 2021