Check out the new Scylla Release!
The Scylla team is pleased to announce the release of Scylla 1.7.5, a bugfix release of the Scylla 1.7 stable branch. Release 1.7.5, like all past and future 1.x.y releases, is backward compatible and supports rolling upgrades. If you are upgrading from 1.6.x to 1.7.5, make sure to read the Scylla 1.7 release notes first. In particular, some of the metric names have changed.
System Impacts – read carefully
Due to a bug (#2752 see below) in the 1.7.x experimental Counters features, upgrading to 1.7.5 may cause updates to counters values. If you are using experimental Counters in 1.7.4, let us know and we will guide you on evaluating the effect before the upgrade.
Bugs fixed in this release:
- Counters: Updating from 1.7.4 to 2.0 breaks counters values #2752 (see system impact above)
- Install: installing Scylla on CentOS ignore patch version when specified #2642
- Init: Scylla init might never complete, get into a deadlock #2623
- Init: On rare occasions, Scylla might core dump when joining a cluster #2652
- Init: Repair starting before node in NORMAL state may cause a core dump #2723
- Init: Unable to start nodes with authenticator parameters #2273
- Shutdown: Scylla shutdown can get into infinite recursion when using TLS (secure connection) #2691, #2690
- Scylla may write incorrect cell names in promoted index blocks #2333
- Failing to write an index file, for any reason, may result in a Scylla crash #2673
- A rare race condition may cause Scylla to exit with “Assertion `_state != state::future’ failed.” message #2697
Data update concurrent with schema update may fail with “attempted to mutate using not synced schema” #2617