The ScyllaDB team announces ScyllaDB Open Source 5.4.8, a bugfix release of the ScyllaDB 5.4 stable branch. ScyllaDB Open Source 5.4.8, like all past and future 5.x.y releases, is backward compatible and supports rolling upgrades.
Note that the latest ScyllaDB Open Source stable release is 6.0 and you are encouraged to upgrade to it.
Related links:
- ScyllaDB Open Source 5.4.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 5.2.x to 5.4.y
- Please let us know if you encounter an issue.
Issue fixed in this release:
- bloom-filter: default value for components_memory_reclaim_threshold is too strict #18607. Updated from 0.1 to 0.2 in the fix.
- Stability: chunked_vector::reserve_partial does not work as documented if size > max_chunk_capacity() #19254
- Stability: node running out of memory and crash during index building and topology change #17476. The root cause is storage_proxy::_throttled_writes may grow without bound #1834
- Stability: sstable_manager: components reloader fiber should run with maintenance scheduling group #18675
- MV: ScyllaDB disseminates the materialized view update backlog in order to control update rates. A bug that prevented this in some circumstances was fixed. #18462
- Stability: messaging_service: add streaming/maintenance tenant to statement tenants. The result is Alternator might keep TTL work in the wrong scheduling group #18719