ScyllaDB Open Source 3.1.4

The ScyllaDB team announces the release of ScyllaDB Open Source 3.1.4, a bugfix release of the ScyllaDB 3.1 stable branch. ScyllaDB Open Source 3.1.4, like all past and future 3.x.y releases, is backward compatible and supports rolling upgrades.

Please note the latest stable ScyllaDB release is 3.2.2, and 3.3 is in the RC phase.

Once 3.3 is released, we will stop support for the 3.1.x release.

Related links:

Issues fixed in this release

  • Correctness: Hinted handoff (HH) sends counter hints as counter updates when a node targeted by the hint does not exist. This may cause wrong counter value when HH is enabled, counters are used, and nodes are down. #5833 #4505
  • Correctness: wrong encoding of a negative value of type varint. More details in #5656
  • Security: fix potential issue in reading YAML from Python #5630
  • Stability: Commitlog uses incorrect IO class while zeroing segments. This may cause commitlog writes waiting on a segment to be delayed for a long time. #5858
  • Stability: using an invalid time UUID can cause ScyllaDB to exit. For example “select toDate(max(mintimeuuid(writetime(COLUMN))))#5552
  • Stability: ScyllaDB crash at init if the io_properties file contains 0-s in write_bandwidth or write_iops #5360
  • Stability: rare error during repair: “runtime error: load of value 48, which is not a valid value for type ‘bool’”  #5531
  • Stability: wrong handling of a case in which ScyllaDB can not write coredumps #5560
  • Stability: downgrade assert on row: append(): downgrade to an error. The assertion, proved to be too strict, aborting on cases which are not fatal. #5786
  • Build: dbuild builds fail on large machines with newish docker/kernel #5651
  • Performance (Streaming): Do not invalidate cache if no sstable is added in flush_streaming_mutations #5769
  • Upgrade: Fail rollback on Debian #5734

[1] Note: if and only if you installed a fresh ScyllaDB 3.1.0, you must add the following line to scylla.yaml of each node before upgrading to 3.1.4:

enable_3_1_0_compatibility_mode: true

This is not relevant if your cluster was upgraded to 3.1.0 from an older version, or you are upgrading from or to any other ScyllaDB releases, like 3.1.1.

If you have doubts, please contact us using the user mailing list.

04 Mar 2020