Scylla Open Source 3.3.2

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

Note that the latest stable branch of Scylla Open Source is Scylla 4.0; you are encouraged to upgrade to it.

Related links:

Issues fixed in this release

  • Stability: When speculative read is configured a write may fail even though enough replicas are alive #6123
    Tools: fstrim service runtime error “NameError: name 'k' is not defined” in scylla_util.py #6294
  • Stability: running with Trace log level and counters cause an abort #5616
  • Stability: in some rare cases, sstable metadata in memory is not correctly evicted, causing memory bloat #4951
  • Stability: nodetool cleanup leaves the data in replica’s cache #4446
  • Stability: malformed replication factor is not blocked in time, causing an error when running DESCRIBE SCHEMA later #3801
  • Stability: multishard_writer can deadlock when producer fails, for example when, during a repair, a node fail #6241
  • Stability: possible query failure, crash if the number of columns in a clustering key or partition key is more than 16 #5856
  • Nodetool/REST API: snapshot with table specified but not keyspace crashes #6336
  • Alternator: Generating timestamps for auth signatures used a non-thread-safe, causing “Signature not yet current” in the client when authentication enabled #6345
  • Alternator: error the “Date” header format breaks aws-sdk-java #6253
  • Alternator: scylla_alternator_total_operations metric was not updated #5836
  • Alternator: write failure when GSI has two new key columns and one has no value #6008

17 May 2020