The ScyllaDB team announces ScyllaDB Enterprise 2024.1.3, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2024.1 LTS Release.
2024.1.3 patch release includes multiple minor bug fixes.
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):
- Stability: frozen_mutation::unfreeze() stall in schema_tables.cc: calculate_schema_digest. The issue (stalls) manifest on cluster with a large schema #17841
- Stability: a theoretical race when reading encryption_file_io_extension may lead to undefined behavior.
- Stability: rare issue when table drop concurrent to any repair #16899, #15425.
- Stability: streaming might fail when a table is dropped. Streaming can be part of a repair, topology change (adding/removing a node), etc. #15370, #17028, #15598
- Stability: in rare cases, nodetool getsstables or calling REST API /column_family/sstables/by_key/ can crash the server #17232
- Stability: Potential data resurrection if regular compaction races with cleanup #17501
- Stability: reader_permit::get_schema() is unsafe against table schema alter or drop #16180
- Stability: Sporadic repair failure when adding a node #16821
- Stability: a very rare use-after-free in sstables::key_view::explode() can be caused by a large enough partition key #17625
- Stability: fair_queue: Do not pop unplugged class immediately. The issue can manifest with a crash during cleanup: [seastar/src/core/fair_queue.cc:222: void seastar::fair_queue::pop_priority_class seastar#eb093f8
- Set up: iotune doesn’t close files that weren’t correctly opened, for example when test directory creation failed for whatever reason, leading to iotune crash. seastar#b9fd21d
- Alternator: a bug in Alternator GSI updates of range key when using two new key columns in GSI #17119
- CQLsh: COPY TO STDOUT is broken #17451
- Scylla AMI for EC2: Cannot get EC2 user data after enabled IMDSv2 scylla-machine-image#498