See all blog posts

ScyllaDB release: version 1.6.5

scylla release
The ScyllaDB team is pleased to announce the release of ScyllaDB 1.6.5, a bugfix release of the ScyllaDB 1.6 stable branch. Note that the latest stable release is ScyllaDB 1.7.1, you are encouraged to upgrade to it.
Release 1.6.5, like all past and future 1.x.y releases, is backward compatible and supports rolling upgrades.  If you are upgrading from 1.5.x to 1.6.5, make sure to read ScyllaDB 1.6 release notes first. In particular, some of the metric names have changed.

Related links

The following bugs were fixed in this ScyllaDB release:

  • CQL SELECT: on some cases, reading from a large partition using WHERE restrictions on the clustering key, can return old values since some tombstones are ignored.  #2326
  • CQL SELECT:  In some cases, a query with CQL SELECT from a large partition (>10MB) may only return subset of the stored rows  #2327
  • scylla_setup: script may fail when bonding iface configuration #2269
  • Gossip: slow connections between Data Centers (DC) when bootstrapping a node may cause a segmentation fault  #2341
  • Repair: Repair of large dataset (1TB) streams too much data than needed #2299
  • Nodetool: nodetool status reports the wrong used disk space #1592
  • ScyllaDB Core: removing temporary sstables uses a lot of memory #2384
  • ScyllaDB Core: reading a large partition, may, in rare cases, invoke undefined behavior #2377
  • ScyllaDB Core: a failed flush, for example when out of disk space, leaves behind a subset of the sstable files #2407

About Tzach Livyatan

Tzach Livyatan has a B.A. and MSc in Computer Science (Technion, Summa Cum Laude), and has had a 15 year career in development, system engineering and product management. In the past he worked in the Telecom domain, focusing on carrier grade systems, signalling, policy and charging applications.