The ScyllaDB team announces the release of ScyllaDB Open Source 3.0.7, a bugfix release of the ScyllaDB Open Source 3.0 stable branch. ScyllaDB Open Source 3.0.7, like all past and future 3.x.y releases, is backward compatible and supports rolling upgrades.
Related links:
- ScyllaDB Open Source 3.0
- Get ScyllaDB Open Source 3.0.7 – Docker, binary packages, and EC2 AMI
- Get started with ScyllaDB
- Upgrade from ScyllaDB Open Source 3.x.y to ScyllaDB Open Source 3.x.z
- Upgrade from ScyllaDB Open Source 2.3.x to 3.0.x
- Please let us know if you encounter any problems.
Issues solved in this release:
- “mc” SSTable file format: empty counters were not handled correctly, which could lead to Coredump #4363. Note that mc format is disabled by default in 3.0. More on mc (Apache Cassandra 3.0 format) here
- Range scan: in a rare condition, a specific combination of data and its alignment in the reader buffer, can lead to missing rows from a range scan #4418. Two things are needed to trigger this defect:
-
- A range tombstone that has the same start bound as the row just after it in the stream
- This range tombstone is the *last* fragment in the reader’s buffer, and that the reader is evicted after the buffer is consumed.
- TimeWindowCompactionStrategy: on some very rare cases, a use after free may hurt performance #4465
- Heat Weighted Load Balancing: on some cases, calculation the HWLB for a large number of tables may cause stalls which will be seen as latency spikes. See commit
31 May 2019
