The ScyllaDB team is pleased to announce the release of ScyllaDB 1.6.3, a bugfix release of the ScyllaDB 1.6 stable branch.
Release 1.6.3, like all past and future 1.x.y releases, is backward compatible and supports rolling upgrades. If you are upgrading from 1.5.x to 1.6.3, make sure to read ScyllaDB 1.6 release notes first. In particular, some of the metrics have changed.
Related links
- Get started with ScyllaDB 1.6.3 here.
- Upgrade from 1.5.x to 1.6.3
- Upgrade from 1.6.x to 1.6.3
- ScyllaDB 1.6 release
- Please let us know if you encounter any problems.
The following bugs were fixed in this ScyllaDB release:
- Two storage_proxy metrics had the same name, ‘throttled_writes” One of them is now named “current_throttled_writes” #
2163 -
ScyllaDB generated std::bad_alloc error when running commitlog replay (after unexpected restart) #2098
-
ScyllaDB Docker image: Prometheus port is now open by default #1827
- ScyllaDB (and Cassandra) golang driver, gocql, may crash when Probabilistic Tracing or Slow Query Log are enabled #2179
- Commitlog replay, after a ScyllaDB restart, can fail with std::out_of_range #2173
- Using Node-to-node SSL gave the wrong logs message. It have been updated to “Starting Encrypted Messaging Service on SSL port…” #1845
- In some cases, ScyllaDB service (scylla-server.service) does not start after running scylla_setup and restarting the server #2236
