The ScyllaDB team announces ScyllaDB Open Source 6.0.3, a bugfix patch release of the ScyllaDB 6.0 stable branch. ScyllaDB Open Source 6.0.3, like all past and future 6.x.y releases, is backward compatible and supports rolling upgrades.
Note that the latest open-source stable branch is 6.1, and you are encouraged to upgrade to it.
Related links:
- ScyllaDB Open Source 6.0.0
- Get ScyllaDB Open Source - AWS AMI, GCP Docker, binary packages and unified installer
- ScyllaDB Web Installer for Linux (all releases)
- Upgrade from ScyllaDB Open Source 6.x.y to Scylla Open Source 6.x.z
- Upgrade from ScyllaDB Open Source 5.4.x to 6.0.y
- Please let us know if you encounter an issue.
Issue fixed in this release:
- Performance: If the CPU is busy processing a query, ScyllaDB will let that query complete before starting another one, since several queries using the CPU concurrently on a shard will make all of them slower. There is now an option to allow increasing CPU concurrency on queries for workloads where this helps. #19017
- Stability (MV): ScyllaDB abort, on a race condition between MV sync and node remove #19754
- 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
- Stability (MV): test_changes_while_node_down: write failures to view metadata tables during node shutdown #18929
- Stability: A bug in DESCRIBE SCHEMA when describing indexes on collection columns was fixed. #19278
- Stability(Tablets): Creating a table allocates tablets on the node being decommissioned #20032
- Stability(LWT): in rare cases, the coordinator sometimes runs multiple transactions on the same key in parallel #19698
- Stability: malformed_sstable_exception due to reload of bloom filters from unlinked sstables #19722
- Stability: In rare cases, ScyllaDB might crash while inserting a mutation into memtable or cache. #19552
- Stability: writes have a server memory footprint even after an acknowledgment is returned to the client, in order to track writes to replica past the consistency level requirement. In one case, CL=ANY and all the target replicas DOWN, writes were kept even after all replicas acknowledged, increasing server memory load, and possibly preventing topology changes from making progress. This scenario can be generated internally when writing to a materialized view. #19529
- Stability: A crash in the REST API call to get the Raft group 0 leader. #19714
- Stability(raft): shutdown phase can get stuck #19223 (found on repair testing)
- Stability: dropping a table while counter update operations are running causing assert at #20015
- Stability: A crash in certain cases of schema changes while an sstable was being written was fixed. #16065
- Monitoring: storage_proxy: LWT contention metric is not initialized #19654
- API: Alternator “/localnodes” request returns nodes which are still joining #19694
- setup(scylla_raid_setup): install update-initramfs when it’s not available. #19871
- hinted handoff: Migrate sync point to host ID #18653. This is part of a bigger effort of using UUID not IPs as host identifier.