Scylla Enterprise 2019.1.13

The ScyllaDB team announces the release of Scylla Enterprise 2019.1.13, a production-ready Scylla Enterprise patch release. As always, Scylla Enterprise customers are encouraged to upgrade to Scylla Enterprise 2019.1.13 in coordination with the Scylla support team. Scylla Enterprise 2020.1 is also available, and customers are encouraged to upgrade to it.

Scylla Enterprise 2019.1.13 fixes a number of reliability issues. More below.

Related Links

  • Get Scylla 2019.1.13 (customers only, or 30-day evaluation)
  • Upgrade from 2019.1.x to 2019.1.13
  • Upgrade from 2018.1.x to 2019.1
  • Upgrade from Scylla Open Source 3.0 to Scylla 2019.1
  • Submit a ticket

Issue fixed in 2019.1.13 with open source references where available:

  • Stability: Scylla Setup recognizes only a single IO Queue, and Scylla fails to start
  • Stability: ScyllaCloud Cluster nodetool cleanup causing long stalls
  • Stability: huge task-quota violations after temporary network outage
  • Stability: crash in get_sstables_by_partition_key REST call
  • Stability: Reduce the amount of maps and sets and general complexity of endpoint calculation by simply mapping dc’s to expected node counts, re-using endpoint sets and iterate thusly. scylla: locator::network_topology_strategy::calculate_natural_endpoints() causing stalls #2896
  • Stability: The Thrift front-end didn’t check the order of clustering ranges in the read command so out-of-order ranges cold propagate to the storage back-end resulting in crashes or incorrect reads. #6498
  • Stability: Sporadic failures building Debian related to fakeroot #6655
  • Stability: Hinted Handoff: memory leak caused by improper commitlog usage from hints manager #6776
  • Stability: fix small aligned free memory corruption; boost/mutation_reader_test failure due to over-aligned (std::align_val_t) dynamic allocation bug in seastar #6831
  • Stability: STREAM_MUTATION_FRAGMENTS: print errors in receive and distribute phase #4901
  • Stability: get_sstables_by_partition_key(): don’t make a copy of selected sstables #7060
  • Performance: Workaround for a performance regression in kernel-ml 5.8.0, 5.8.1 in AWS i3en. Pin down kernel version used for AWS image until the performance regression is fixed #7036

27 Aug 2020