The ScyllaDB team is pleased to announce the release of ScyllaDB Enterprise 2017.1.2, a production-ready ScyllaDB Enterprise minor release.
ScyllaDB Enterprise 2017.1.2 is a bug fix release for the 2017.1 branch, the latest stable branch of ScyllaDB Enterprise.
The 2017.1 branch is based on ScyllaDB open source 1.6 and includes backports bug fixes from upstream releases (1.7, 2.0, 2.1) as well as enterprise-only bug fixes.
Read more about ScyllaDB Enterprise here.
Related Links
- Get ScyllaDB 2017.1.2 (customers only, or 30-day evaluation)
- Upgrade from 2017.1.x to 2017.1.2
- Upgrade from ScyllaDB 1.6 to ScyllaDB 2017.1
- Submit a ticket
ScyllaDB Enterprise customers are encouraged to upgrade to ScyllaDB Enterprise 2017.1.2 and are welcome to contact our support with questions.
Noteworthy bug fixes
- A rare race condition may cause ScyllaDB to exit with “Assertion `_state != state::future’ failed.” message #2697
- Repair: Do not allow repair until node is in NORMAL status #2723
- Generating sstable sharding metadata can cause long latencies #2707
- Nodetool refresh is stuck when respective column family is being loaded in parallel #2769
- Coordinator-side speculative retry does not use read latency measurements from replicas #2757
Notable additions
- scyllarepair – the recurrent repair script is delivered as part of the ScyllaDB Enterprise packages
- ScyllaDB stall detector and the large allocation detector are delivered as part of the ScyllaDB Enterprise 2017.1.2
Both tools report to the log and will help ScyllaDB support team to identify potential issues.
