ScyllaDB Open Source Release 3.0.10

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

Related links:

• ScyllaDB Open Source 3.0
• Get ScyllaDB Open Source 3.0.10 – 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
• Upgrade from ScyllaDB Open Source 2.3.x to 3.0.x
• Please let us know if you encounter any problems.

Issues solved in this release:

• Stability: Possible race condition between compaction deleting sstable and reshuffling of sstable, for example when migrating data from Apache Cassandra, or ScyllaDB server with a different core number. #4622
• Stability: ScyllaDB may hang or even segfaults when querying system.size_estimates #4689
• An issue in command-line options parsing, prevents ScyllaDB Docker from starting, reporting “error: too many positional options have been specified on the command line” error #4141
• Stability: Catch SSTable unclosed partition format error in the write path, not in the read path. A new command line flag: --abort-on-internal-error make ScyllaDB exit as soon as such an error occurs, making it easier to catch and debug. #4794, #4786
• Stability: Receiving side of streaming may abort or produce incorrect sstables when failure happens on the sender side, generate the following error:
  sstables/sstables.cc:1748: void sstables::seal_summary(sstables::summary&, std::experimental::fundamentals_v1::optional&&, std::experimental::fundamentals_v1::optional&&, const sstables::index_sampling_state&): Assertion `first_key' failed. #4789
• Stability: A node restart during repair may cause the node streaming data to it to abort with an error message:
  scylla: message/messaging_service.cc:549: seastar::shared_ptr netw::messaging_service::get_rpc_client(netw::messaging_verb, netw::messaging_service::msg_addr): Assertion `!_stopping' failed.
Aborting on shard 1. #4767
• Stability: In some cases, when --abort-on-lsa-bad-alloc is enabled, ScyllaDB aborts even though it’s not really out of memory #2924
• Stability: Potential undefined behavior in sstables cleanup, which may cause a segmentation fault #4718
• Stability: When using MC sstable format, ScyllaDB might fail to exit gracefully in out of disk space error: #4614
• Stability: A possible deadlock between connection authentication and the stall detector, in case the authentication logic generates a stall #4759
• Stability: Exceptions in index reader are not handled gracefully #4761