ScyllaDB Open Source 3.1.3

The ScyllaDB team announces the release of ScyllaDB Open Source 3.1.3, a bugfix release of the ScyllaDB 3.1 stable branch. ScyllaDB Open Source 3.1.3, 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.1, 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:

• ScyllaDB Open Source 3.1
• Get ScyllaDB Open Source 3.1.3 – Docker, binary packages, and EC2 AMI
• Get started with ScyllaDB
• Upgrade from ScyllaDB Open Source 3.x.y to ScyllaDB Open Source 3.x.z [1]
• Upgrade from ScyllaDB Open Source 2.3.x to 3.0.x
• Please let us know if you encounter any problems.

Issues fixed in this release

• Stability: updates of MVs, for example after a node restart, can take too much IO resources from on-line requests, increasing their latency. #4615
• Stability: User Defined Types (UDT) in columns with descending order may fail #4672
• Stability: ALTER of a nested UDT will fail when user try to insert data into the new type #5049
• Stability: running a mis formatted ALTER command on a UDT will cause a crush #4837
• Stability: a graceful shutdown fais produce an an error when Tracing is on
  [with Service = tracing::tracing]: Assertion `local_is_initialized()’ #5243
• Stability (ARM): possible Use-after-move in make_multishard_streaming_reader() #5419
• CQL: error formats field name as a hex string instead of text #4841
• Performance: Materialized views use scan readers for single-partition scans during read-before-write which causes read amplification #5418
• Install: ubuntu/debian missing scyllatop files #5518

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.

19 Feb 2020