The ScyllaDB team announces ScyllaDB Open Source 5.0.4, a bugfix release of the ScyllaDB 5.0 stable branch.
ScyllaDB Open Source 5.0.4, like all past and future 5.x.y releases, is backward compatible and supports rolling upgrades.
- ScyllaDB Open Source 5.0
- Get ScyllaDB Open Source – AWS AMI, GCP Docker, binary packages and unified installer
- ScyllaDB Web Installer for Linux (all releases)
- Upgrade from ScyllaDB Open Source 5.x.y to Scylla Open Source 5.x.z
- Upgrade from ScyllaDB Open Source 4.6.x to 5.0.y
- Please let us know if you encounter any problems.
Issues fixed in this release:
- Stability: Docker image fails to run Alternator with HTTPS. #10025
- Performance: Long-term index caching in the global cache, as introduced in 4.6, hurts the performance for workloads where accesses to the index are sparse. To mitigate this, a new configuration parameter
true) is introduced to control index caching. Setting the flag to `
false` causes all index reads to behave like they would in
BYPASS CACHEqueries. Consider using
falseif you notice performance problems due to lowered cache hit ratio in 4.6 or 5.0. The config API can update the parameter live (without restart). #11202
- Stability: Some shards get stuck in tight loop during repair #11223. This is a regression introduced in ScyllaDB 5.0
- Stability: lack of mutation associativity which manifests as sporadic failures in
- Stability: Messaging service misconfigured
tcp_nodelayfor verbs. The result is gossiper messages are coming with increased latency. This may affect the nodes status visibility of each other and, which is worse, there’s an increased chance of one node marking the alive peer as dead #11465
- Alternator Stability: Invalid
alternator_encryption_optionsin scylla.yaml causes ScyllaDB to coredump. #11520
scylla sstable --helpis broken #11571
03 Oct 2022