The ScyllaDB team announces ScyllaDB Enterprise 2024.1.9, a bug-fix production-ready patch release for ScyllaDB Enterprise 2024.1 LTS Release.
Related Links
- Get ScyllaDB Enterprise 2024.1 (customers only, or 30-day evaluation)
- Upgrade from ScyllaDB Enterprise 2023.1.x to 2024.1.y
- Upgrade from ScyllaDB Enterprise 2022.2.x to 2024.1.y
- Upgrade from ScyllaDB Open Source 5.4 to ScyllaDB Enterprise 2024.1.x
- Submit a ticket
The following issues are fixed in this release (with an open-source reference, if available):
- Upgrade: Upgrade fails when the number of service levels close to the max. The root cause is ScyllaDB did not correctly identify internal scheduling groups, for example for maintenance, and tried to create service levels for them. #20070
- Performance: streaming JSON values was adjusted to avoid stalls. The destruction of these large JSON values now also avoids stalls #19968
- Stability: a race between table drop and a counter column update. #19948
- Stability (Gossip): gossiper::add_saved_endpoint uses the local heart_beat_state if the ep_state already exists #16429
- Monitoring: adding batch latency and batch size metrics to Alternator #20190. Batch sizes are implemented as ever-growing counters. To get the average batch size divide the rate of the batch size counter by the rate of the number of batch counter:
- rate(batch_get_item_batch_size)/rate(batch_get_item)
- Tooling: The scylla sstable command can now recover the schema from the SStable itself, if it is new enough (ma format or later). #17869 #18809