ScyllaDB Open Source 3.2.2

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

The most urgent fix is for users using both Hinted Handoff and Counters. More below.

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: Materialized view updates with future partition tombstones are not correctly generated. When the base table does not have any rows, but it does have a partition tombstone with a given timestamp, inserting a base row with a smaller timestamp will generate an incorrect materialized view update #5793
  • 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: 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
  • Upgrade: Fail rollback to 3.2 (from ScyllaDB 3.3) on Debian #5734
  • Install: Installation of Debian fails with error: “scylla_post_install.sh: fail to get a valid (integer) memory size#5569
  • Stability (LWT): writes to local.paxos create small sstables and cause a lot of compaction activity #5682
  • Stability (LWT): better reports for LWT timeouts #5598
  • Build: dbuild builds fail on large machines with newish docker/kernel #5651
  • Stability (LWT): Fix the handling of nulls in parameter markers for LWT queries #5710
  • 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
  • Performance (Streaming): Do not invalidate cache if no sstable is added in flush_streaming_mutations #5769

28 Feb 2020