The ScyllaDB team announces ScyllaDB Enterprise 2023.1.9, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2023.1 LTS Release.
2023.1.9 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):
- Stability: Conversion of timestamp column to JSON and back fails #16575, #14518
- Stability: direct failure detector: make ping timeout configurable and increase the default, from 300 to 600 ms #16607. Failure detector is an internal inter-node mechanism.
- Stability: mutation_fragment_stream_validating_filter doesn’t respect validation_level::none #18662. The issue might cause false-positive validation errors during repair/streaming, leading to aborting the operation.
- Stability: utils::chunked_vector fill constructor is exception unsafe #18635
- Tracing: Reader concurrency semaphore now has more tracepoints, useful with CQL tracing. #12781
Bloom Filter related
- Performance: ScyllaDB estimates a compaction’s partition count in order to correctly size the Bloom filter. It will now improve the estimate for garbage collection SStables. #18283,
- bloom-filter: default value for components_memory_reclaim_threshold is too strict #18607. Updated from 0.1 to 0.2 in the fix.