Oct25

New Maintenance Releases for Scylla Enterprise and Scylla Open Source

Subscribe to Our Blog

Scylla Release

The Scylla team announces the availability of three maintenance releases: Scylla Enterprise 2018.1.6, Scylla Open Source 2.3.1 and Scylla Open Source 2.2.1. Scylla Enterprise and Scylla Open Source customers are encouraged to upgrade to these releases in coordination with the Scylla support team.

  • Scylla Enterprise 2018.1.6, a production-ready Scylla Enterprise maintenance release for the 2018.1 branch, the latest stable branch of Scylla Enterprise
  • Scylla Open Source 2.3.1, a bug fix release of the Scylla Open Source 2.3 stable branch
  • Scylla Open Source 2.2.1, a bug fix release of the Scylla Open Source 2.2 stable branch

Scylla Open Source 2.3.1 and Scylla Open Source 2.2.1, like all past and future 2.x.y releases, are backward compatible and support rolling upgrades.

These three maintenance releases fix a critical issue with nodetool cleanup:

nodetool cleanup is used after adding a node to a cluster, to clean partition ranges not owned by a node. The critical issue we found is that nodetool cleanup would wrongly erase up to 2 token ranges that were local to the node. This problem will persist if cleanup is executed on all replicas of this range. The root cause of the issue is #3872, an error in an internal function used by cleanup to identify which token ranges are owned by each node.

If you ran nodetool cleanup, and you have questions about this issue, please contact the Scylla support team (for Enterprise customers, submit a ticket; for Open Source users, please let us know via GitHub).

Related Links for Scylla Enterprise 2018.1.6

Related links for Scylla Open Source

Additional fixed issues in Scylla Enterprise 2018.1.6 release, with open source references, if they exist:

  • CQL: Unable to count() a column with type UUID #3368, Enterprise #619
  • CQL: Missing a counter for reverse queries #3492
  • CQL: some CQL syntax errors can cause Scylla to exit #3740#3764
  • Schema changes: race condition when dropping and creating a table with the same name #3797
  • Schema compatibility when downgrading to older Scylla or Apache Cassandra #3546
  • nodetool cleanup may double the used disk space while running #3735
  • Redundant Seastar “Exceptional future ignored” warnings during system shutdown. Enterprise #633 

Additional issues solved in Scylla Open Source 2.2.1:

  • CQL: DISTINCT was ignored with IN restrictions #2837
  • CQL: Selecting from a partition with no clustering restrictions (single partition scan) might have resulted in a temporary loss of writes #3608
  • CQL: Fixed a rare race condition when adding a new table, which could have generated an exception #3636
  • CQL: INSERT using a prepared statement with the wrong fields may have generated a segmentation fault #3688
  • CQL: failed to set an element on a null list #3703
  • CQL: some CQL syntax errors can cause Scylla to exit #3740#3764 – Performance: a mistake in static row digest calculations may have lead to redundant read repairs #3753#3755
  • CQL: MIN/MAX CQL aggregates were broken for timestamp/timeuuid values. For example SELECT MIN(date) FROM ks.hashes_by_ruid; where the date is of type timestamp #3789
  • CQL: TRUNCATE request could have returned a succeeds response even if it failed on some replicas #3796
  • scylla_setup: scylla_setup run in silent mode should fail with an appropriate error when mdadm fails #3433
  • scylla_setup: may report on “NTP setup failed” after successful setup #3485
  • scylla_setup: add an option to select server NIC #3658
  • improve protection against out of memory while which insert a cell to existing row #3678
  • Under certain, rare, circumstances a scan query can end prematurely, returning only parts of the expected data-set #3605

Additional issues solved in Scylla Open Source 2.3.1:

  • Gossip: non zero shards may have stale (old) values of gossiper application states for some time #3798. This can create an issue with schema change propagation, for example, TRUNCATE TABLE #3694
  • CQL: some CQL syntax errors can cause Scylla to exit #3740#3764
  • In Transit Encryption: Possible out of memory when using TLS (encryption) with many connections #3757
  • CQL: MIN/MAX CQL aggregates were broken for timestamp/timeuuid values. For example SELECT MIN(date) FROM ks.hashes_by_ruid; where the date is of type timestamp #3789
  • CQL: TRUNCATE request could have returned a succeeds response even if it failed on some replicas #3796
  • Prometheus: Fix histogram text representation #3827

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: maintenance release, open source, release notes, Scylla Enterprise, Scylla Open Source