The ScyllaDB team announces ScyllaDB Enterprise 2021.1.14, 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.14 brings focus on bug fixes and stabilization.
Related Links
- Get ScyllaDB Enterprise 2021.1.14 (customers only, or 30-day evaluation)
- Upgrade from 2020.1.x to 2021.1.y
- Upgrade from ScyllaDB Open Source 4.3 to Scylla Enterprise 2021.1
- Submit a ticket
Below is a list of performance and stability improvements and bug fixes, each with an open source reference:
- UX: misleading error message on logs. Currently, our error message on
scylla_preparesays “Exception occurred while creating perftune.yaml“, even if perftune.yaml is already generated, and an error occurred after that. #10575 - Monitoring: When computing moving average rates too early after startup, the rate can be infinite; the cause is sample interval since the system started is too small to generate meaningful results. #4469
- Performance: background reclaim shares were not adjusted in a timely manner.
- Stability: Row cache will miss a row if the upper bound of the population range is evicted and has an adjacent dummy row #11239
- Stability: Accidentally quadratic behavior when a large number of range tombstones is present in a partition has been fixed. #11211
- Stability: Scylla propagates cache hit rate information through gossip, to allow coordinators to send less traffic to a newly started node. It will now spend less effort to do so on large clusters. #5971
- Service Level stability: Fix a race condition between RPC and Service Level creation that may cause some service levels to use the default scheduling group on some nodes. The result can cause a workload using the wrong service level, getting more or less resources than intended, and in extreme cases can cripple some workloads entirely.
01 Sep 2022
