The ScyllaDB team announces the release of ScyllaDB Enterprise 2018.1.11, a production-ready ScyllaDB Enterprise minor release. ScyllaDB Enterprise 2018.1.11 is a bug fix release for the 2018.1 branch, the latest stable branch of ScyllaDB Enterprise. As always, ScyllaDB Enterprise customers are encouraged to upgrade to ScyllaDB Enterprise 2018.1.11 in coordination with the ScyllaDB support team.
The major fix in this release is for a rare race condition between a schema update (adding or removing a column) and an initiated compaction, which may cause the compaction to write values to the wrong columns. The short time window where this may occur, is just after compaction was initiated but before it starts writing to storage. Should the race condition occur, there may be a crash or validation/run-time error on the driver side. #4304
Other fixes issues in this release are listed below, with open source references, if present:
- Using ScyllaDB shard aware drivers may cause unbalanced connections, where one shard has tens of thousands of connections, while the others do not, resulting in a temporary slow down #4269
- Reads from system tables do not time out as they should, which might create large queues of reads if connections were opened too often.
- Rebuilding a node may cause long reactor stalls on large clusters #3639
- A bootstrapping node doesn’t wait for a schema before joining the ring, which may result in the node failing to bootstrap, with the error
storage_proxy - Failed to apply mutation. In particular, this error manifests when user-defined type is used. #4196 - cqlsh: Make TLSv1.2 default
Related Links
- Get ScyllaDB 2018.1.11 (customers only, or 30-day evaluation)
- Upgrade from 2018.1.x to 2018.1.11
- Upgrade from 2017.1.x to 2018.1
- Upgrade from ScyllaDB Open Source 2.1 to ScyllaDB 2018.1
- Submit a ticket
