The Scylla team is pleased to announce the release of Scylla Enterprise 2017.1.4, a production-ready Scylla Enterprise minor release.
Scylla Enterprise 2017.1.4 is a bug fix release for the 2017.1 branch, the latest stable branch of Scylla Enterprise.
The 2017.1 branch is based on Scylla open source 1.6 and includes backported bug fixes from upstream releases (1.7, 2.0, 2.1) as well as enterprise-only bug fixes.
Read more about Scylla Enterprise here.
Related Links
- Get Scylla 2017.1.4 (customers only, or 30-day evaluation)
- Upgrade from 2017.1.x to 2017.1.4
- Upgrade from Scylla 1.6 to Scylla 2017.1
- Submit a ticket
Scylla Enterprise customers are encouraged to upgrade to Scylla Enterprise 2017.1.4 and are welcome to contact our support with questions.
Noteworthy Bug Fixes with References to Upstream (Open Source) Issues:
-
-
- nodetool status shows stalled status of previous Scylla run. For example, when Scylla exits with an out of disk space error, after a restart,
nodetool statusmay show old and out of date statuses of other nodes in the cluster. #1629 - Unbound LSA memory allocation size may lead to huge memory segment allocation and cause latency issues. #2335
- SSTables are not destroyed if streaming flushes fail – keeping them on disk in a temporary state taking redundant space. #3062
- In some rare cases, LSA zone reclaimer leaks memory in certain conditions, which may result in bad_allocs at a later phase. #3129
- Node fails to restart and crash with error “Assertion `!_in_batch’ failed”. #3018
- Prometheus metrics pulling can cause memory pressure and latency issues. Seastar commit.
- nodetool status shows stalled status of previous Scylla run. For example, when Scylla exits with an out of disk space error, after a restart,
-
The post New Release: Scylla Enterprise 2017.1.4 appeared first on ScyllaDB.