The ScyllaDB team announces ScyllaDB Enterprise 2023.1.10, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2023.1 LTS Release.
2023.1.10 patch release includes multiple minor bug fixes.
ScyllaDB Enterprise’s latest Long Term Support (LTS) is 2024.1. While we continue to support 2023.1, you are encouraged to upgrade to it in coordination with the ScyllaDB Support team.
Related Links
- Get ScyllaDB Enterprise 2023.1 (customers only, or 30-day evaluation)
- Upgrade from ScyllaDB Enterprise 2022.1.x to 2023.1.y
- Upgrade from ScyllaDB Open Source 5.2 to ScyllaDB Enterprise 2023.1.x
- Upgrade from ScyllaDB Enterprise 2023.1.x to 2023.1.y
- Upgrade from ScyllaDB Enterprise 2023.1.x to 2024.1.y
- Submit a ticket
The following issues are fixed in this release (with an open-source reference, if available):
- Security: the new ScyllaDB image (GCP, AWS, Azure, Docker) includes a fix for OpenSSH Vulnerability CVE-2024-6387.
- Alternator Performance: reduce stall for Query and Scan with large pages #18036
- Upgrade from open source to Enterprise:
- server connection dropped: Can’t create scheduling group for $user,
- Tracing: messaging_service prints in the log “$user” instead of service level name
- 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
- There is now configuration “maintenance_reader_concurrency_semaphore_count_limit” for the number of concurrent reads allowed for maintenance operations (e.g. repair). This helps repair in some situations where different nodes have different shard counts. #19248