ScyllaDB Enterprise Release 2019.1.1

The ScyllaDB team announces the release of ScyllaDB Enterprise 2019.1.1, a production-ready ScyllaDB Enterprise minor release. ScyllaDB Enterprise 2019.1.1 is a feature and bugfix release for the ScyllaDB Enterprise 2019.1 branch, the latest stable branch of ScyllaDB Enterprise. ScyllaDB Enterprise customers are encouraged to upgrade to ScyllaDB Enterprise 2019.1.1 in coordination with the ScyllaDB support team.

Additional Features in ScyllaDB Enterprise 2019.1.1

Encryption at rest

You can now encrypt on-disk ScyllaDB data, including:

  • SSTables
  • Commit logs
  • Batch and hints logs

Encryption can be done in a table, keyspace granularity. Encryption keys can be stored locally. Centralized key management with a KMIP server is *not* available in ScyllaDB Enterprise 2019.1.1, and will be included in a future ScyllaDB Enterprise 2019.1.x release.

Known Issues in Encryption at rest:

  • DESCRIBE TABLE with encryption at rest parameters does not have the exact same format as CQL CREATE format. The results, schema backup and restore of tables with encryption at rest will require manual schema updates.

ScyllaDB Enterprise Docker and AMI

(For customers and evaluation)

ScyllaDB Enterprise is now available as a Docker instance and as a EC2 AMI (more regions coming soon)


The new BYPASS CACHE clause on SELECT statements informs the database that the data being read is unlikely to be read again in the near future, and also was unlikely to have been read in the near past; therefore no attempt should be made to read it from the cache or to populate the cache with the data. This is mostly useful for range scans which typically process large amounts of data with no temporal locality and do not benefit from the cache.

For example:

SELECT * from heartrate BYPASS CACHE;

If you are using ScyllaDB Monitoring Stack, you can use the Cache section of the ScyllaDB Per Server dashboard, to see the effect of the BYPASS CACHE command on the cache hit and miss ratio.

  • More on BYPASS CACHE here

Related Links

Additional fixed issues in this release, with open source references, if exist:

  • “mc” SSTable file format: empty counters were not handled correctly, which could lead to Coredump #4363. Note that mc format is disabled by default in 2019.1. More on mc (Apache Cassandra 3.0 format) here
  • Range scan: in a rare condition, a specific combination of data and its alignment in the reader buffer, can lead to missing rows from a range scan #4418. Two things are needed to trigger this defect:
    • A range tombstone that has the same start bound as the row just after it in the stream
    • This range tombstone is the *last* fragment in the reader’s buffer, and that the reader is evicted after the buffer is consumed.
  • TimeWindowCompactionStrategy: on some very rare cases, a use after free may hurt performance #4465

05 July 2019