The ScyllaDB team announces ScyllaDB Enterprise 2023.1.6, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2023.1 LTS Release.
2023.1.6 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):
-
cdc: allow sending writes to the previous generation for some time after switching #7251, #15260. The previous bypass for this issue, retry the request, does not work when using LWT and CDC on the same table. The issue can appear both in CQL CDC and Alternator (Amazon DynamoDB compatible API) Streams.
-
Stability: ScyllaDB locks all memory so we don’t experience high latency due to page faults. However, this only applies from the first time the memory is accessed; the first access can still experience stalls, made larger by using transparent huge pages. #8828.
-
Stability: in rare cases, nodetool getsstables or calling REST API /column_family/sstables/by_key/ can crash the server #17232
-
Stability: query_tombstone_page_limit applies to unpaged queries, while it should not #17241
-
MV Correctness: in some cases, like one base table with many views, updates to MV might be lost. In one example range tombstones made the issue appears earlier #17117
-
Log: schema::describe: print
synchronous_updatesonly when it’s present in extension map #14924 -
Build: Regenerate frozen toolchain for gnutls 3.8.3 and clang clang-16.0.6-4. #17285