Apr6

Scylla release: version 1.6.3

Subscribe to Our Blog

The ScyllaDB team is pleased to announce the release of Scylla 1.6.3, a bugfix release of the Scylla 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 Scylla 1.6 release notes first. In particular, some of the metrics have changed.

Scylla Release

Related links

The following bugs were fixed in this Scylla release:

  • Two storage_proxy metrics had the same name, ‘throttled_writes” One of them is now named  “current_throttled_writes” #2163
  • Scylla generated std::bad_alloc error when running commitlog replay (after unexpected restart)  #2098
  • Scylla Docker image: Prometheus port is now open by default #1827
  • Scylla (and Cassandra) golang driver, gocql,  may crash when Probabilistic Tracing or Slow Query Log are enabled #2179
  • Commitlog replay, after a Scylla 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, Scylla service (scylla-server.service) does not start after running scylla_setup and restarting the server #2236

Tzach LivyatanAbout Tzach Livyatan

Tzach Livyatan has a B.A. and MSc in Computer Science (Technion, Summa Cum Laude), and has had a 15 year career in development, system engineering and product management. In the past he worked in the Telecom domain, focusing on carrier grade systems, signalling, policy and charging applications.


Tags: release