[RELEASE] Scylla 3.0 Release Candidate 1

34 views
Skip to first unread message

Tzach Livyatan

<tzach@scylladb.com>
unread,
Nov 5, 2018, 10:17:51 AM11/5/18
to scylladb-users@googlegroups.com, scylladb-dev@googlegroups.com

The Scylla team is pleased to announce the release of Scylla 3.0 RC1, the first Release Candidate for Scylla 3.0. From now on, only critical bugs will be fixed in branch-3.0. We will continue to fix bugs and add features to the master branch.


The Scylla 3.0 release brings major new features including, production-ready Materialized View, Secondary Index, Hinted Handoff and a new disk format compatible with Apache Cassandra 3.0. The new disk format will be disabled by default, allowing a controlled move to the new format following the upgrade from conservative reasons.


Scylla is an open source, Apache-Cassandra-compatible NoSQL database, with superior performance and consistently low latency. Find the Scylla 3.0 repository for your Linux distribution here (under More Versions).

Use the release candidate with caution; RC1 is not officially production-ready yet. Help us stabilize Scylla 3.0 by reporting bugs here. A list of known issues in this release candidate are listed below


Please note that only the last two minor releases of Scylla open source project are supported. Once Scylla 3.0 is officially released, only Scylla 3.0 and Scylla 2.3 will be supported, and Scylla 2.2 will be retired.


Related Links     

* Get Scylla 3.0 (under “More Versions”)

* Report a problem


New features in Scylla 3.0

* Materialized Views (MV)

With Scylla 3.0, MV is production ready (it was experimental in previous versions) and feature-compatible with Apache Cassandra 3.0, including:

* Creating a MV based on any subset of columns of the base table, including the primary key columns

* Updating a MV for base table DELETE or UPDATE.

* Indexing of existing data when creating an MV

* Support for MV hinted handoff

* Topology changes, and migration of MV token ranges

* Sync of TTL between a base table and an MV table

* nodetool viewbuildstatus

* Unselected columns keep MV row alive #3362, CASSANDRA-13826


The following MV functions are *not* available in Scylla 3.0:

* MV on static and collection columns


* Secondary Index (SI)

Unlike Apache Cassandra, Scylla’s SI is based on MV. This means every secondary index creates a materialized view under the hood, using all the columns of the original base table’s primary key, and the required indexed columns. With Scylla 3.0, SI is production ready, it was experimental in previous versions.


The following SI functions are *not* available in Scylla 3.0

* Indexing of Static and Collection columns (same as for MV above)


* Hinted Handoff (see Scylla 2.2) was experimental in previous versions and is now production ready.


* New File format. Scylla 3.0 includes an Apache Cassandra 3.x file format (mc) which is more efficient and requires less disk space than the Scylla 2.x and Apache Cassandra 2.x format (la). Note that Scylla 3.0 is able to read the old file format


* Full (multi-partition) scan improvement (#1865)

Full scan is a common use case of analytics where one needs to query data *without* a key. In Scylla 3.0, full table scans are significantly improved, with even more optimization coming in following releases.

More on full scans on Scylla 3.0 here


* CQL: Enable ALLOW FILTERING for regular and primary key columns   #2025

For example:

CREATE TABLE t (p int, c int, v int, PRIMARY KEY (p, c));

select * from t where c = 0 and v = 1 allow filtering;

select * from t where p = 0 and v = 1 allow filtering;

select * from t where p = 0 and c = 0 and v = 1 allow filtering;


* Tooling: Move to Cassandra 3.11 Java Tools: including nodetool and cassandra-stress.

* Significant improvements to Scylla streaming reducing the time it takes to repair, add a node to a cluster and other cluster operations which use streaming under the hood. More here.



Known Issues in Release Candidate 1

* Back Pressure for MV is not fully tested yet, resulting in possible performance issues when running with MV or SI #3275 #3756

* SSTable 3.0 format performance is not fully optimized yet #3874 #3868 #3852

* For a full list of Scylla 3.0 issues see here.


Regards
Tzach

Tzach Livyatan

<tzach@scylladb.com>
unread,
Dec 20, 2018, 3:37:16 AM12/20/18
to ScyllaDB users, scylladb-dev

The Scylla team is pleased to announce the release of Scylla 3.0 RC2, the second Release Candidate for Scylla 3.0. From now on, only critical bugs will be fixed in branch-3.0. We will continue to fix bugs and add features to the master branch.


The Scylla 3.0 release brings major new features including, production-ready Materialized View, Secondary Index, Hinted Handoff and a new disk format compatible with Apache Cassandra 3.0. The new disk format is disabled by default, allowing a controlled move to the new format following the upgrade.


Scylla is an open source, Apache-Cassandra-compatible NoSQL database, with superior performance and consistently low latency. Find the Scylla 3.0 repository for your Linux distribution here (under More Versions).

Use the release candidate with caution; RC2 is not officially production-ready yet. Help us stabilize Scylla 3.0 by reporting bugs here.

Please note that only the last two minor releases of Scylla open source project are supported. Once Scylla 3.0 is officially released, only Scylla 3.0 and Scylla 2.3 will be supported, and Scylla 2.2 will be retired.


More on Scylla 3.0 new features below (see the RC1 announcement) 

Fixed issues since 3.0 rc1:
- Materialized Views: Call into view write path when applying streaming mutations #3275
- Streaming: Expose reason for streaming  #3276
- Core: Evict `storage_proxy` write response handlers timely for all cases #3566
- Core: Unable to bootstrap new node #3732
- Core: send_to_endpoint() should consider endpoint liveness #3820
- Setup Scripts: automatic disk tunning, Read latency Very high p99th read latency during "Read only" workload #3831
- Refactoring: Stop using sstable metadata' ancestors  #3852
- SSTables 3.x:  files with empty static row can't be output by sstabledump #3900
- Setup Scripts: scylla-housekeeping-restart.service is misconfigured for Debian/Ubuntu #3906
- Setup Scripts: Scylla_setup: still ask for nic in non-interactive mode #3908
- Materialized Views: Mark MV and SI features as no longer "experimental" #3917- SStable compression changed to be disabled by default https://github.com/scylladb/scylla/issues/3926
- Core: bad_alloc from phased_barrier::advance_and_await() called from memtable flush may cause subsequent flushes to SIGSEGv #3931
- Shutdown process: race in real_mark_alive and handle_shutdown_msg #3940
- SSTables 3.x: Scylla writes component offset map in Statistics.db in the wrong order #3955
- Core: use after free in storage proxy during write timeout #3972
- SSTables 3.x:  Clustering keys with more than 16 components can be corrupted on read if there are missing components on mc format sstables #3973
- Schema agreement: system_distributed keyspace initialization prevents reaching schema agreement #3976
- Sec index: Error out if custom indexes are created #3977

Please let us know if you have any question about Scylla 3.0 or Scylla 3.0 RC2

Regards
Tzach

Avi Kivity

<avi@scylladb.com>
unread,
Dec 20, 2018, 6:39:14 AM12/20/18
to Tzach Livyatan, ScyllaDB users, scylladb-dev
To enable the mc sstable format for your Scylla 3.0 cluster, set

   enable_sstables_mc_format: true

in /etc/scylla/scylla.yaml.
--
You received this message because you are subscribed to the Google Groups "ScyllaDB development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-dev...@googlegroups.com.
To post to this group, send email to scylla...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-dev/CAEB7%3D3ZmkDEvvtJSnCg7aiXSMzmZ4cGXjynnhzx807bNHCWDkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Reply all
Reply to author
Forward
0 new messages