The ScyllaDB team is pleased to announce the release of ScyllaDB 2.0.1, a bugfix release of the ScyllaDB 2.0 stable branch. Release 2.0.1, like all past and future 2.x.y releases, is backward compatible and supports rolling upgrades. If you are upgrading from 1.7.x, make sure to read the ScyllaDB 2.0 release notes first. In particular, you can only upgrade to ScyllaDB 2.0 from ScyllaDB 1.7.4 or later, and support for older versions of drivers have been discontinued (driver support is detailed in the release notes).
Related links:
- Get started with ScyllaDB 2.0
- Upgrade from 1.7.x to 2.0
- Upgrade from 2.0.0 to 2.0.1
- Please let us know if you encounter any problems
Bugs fixed in this release:
- Resharding compactions statistics are not visible to monitoring tools. Resharding can happen when a user updates the number of cores on a ScyllaDB node or moves SSTables from Cassandra or a ScyllaDB node with a different core count. #2671
- In large clusters, for example, 50 nodes or above, slow gossip state propagation, and redundant gossip messaging may lead to replication data being lost during cluster init. #2869, #2855, #764, #2853, #2824
- Reads of static columns may abort or return incorrect data under some conditions. #2880
- On rare conditions, the cache may lose information about range deletions when bad_alloc happens during cache population. #2938
