The ScyllaDB team is pleased to announce the release of ScyllaDB 1.7.1, a bugfix release of the ScyllaDB 1.7 stable branch.
Release 1.7.1, like all past and future 1.x.y releases, is backward compatible and supports rolling upgrades. If you are upgrading from 1.6.x to 1.7.1, make sure to read ScyllaDB 1.7 release notes first. In particular, some of the metrics have changed.
Related links
- Get started with ScyllaDB 1.7 here.
- Upgrade from 1.6.x to 1.7.x
- Upgrade from 1.7 to 1.7.1
- ScyllaDB 1.7 release
- Please let us know if you encounter any problems.
The following bugs were fixed in this ScyllaDB release:
- removing temporary sstables uses a lot of memory #2384
- reading a large partition, may, in rare cases, invoke undefined behavior #2377
- compaction does not immediately purge fully expired sstables #2249, #2253
- repair and decommission streams are closed after 600 seconds, although streaming is still active #2197
- a failed flush, for example when out of disk space, leaves behind a subset of the sstable files #2407
- Nodetool: nodetool status reports the wrong used disk space #1592
- Nodetool: nodetool cfstats is not reporting space used by bloom filters #2449
- ScyllaDB tools: java tools, like sstabledump, report “Could not find or load main class” error #2414
- ScyllaDB tools: sstableloader might drop clustering information in some cases scylla-tools #31 , #2443
- build on Debian Jessie fail #2444, #244
5, #2451
