The ScyllaDB team announces the release of ScyllaDB Enterprise 2019.1.21, a production-ready ScyllaDB Enterprise patch release. As always, ScyllaDB Enterprise customers are encouraged to upgrade to ScyllaDB Enterprise 2019.1.21 in coordination with the ScyllaDB support team. ScyllaDB Enterprise 2020.1 is also available, and customers are encouraged to upgrade to it.
ScyllaDB Enterprise 2019.1.21 fixes two issues. More below.
Related Links
- Get ScyllaDB 2019.1.21 (customers only, or 30-day evaluation)
- Upgrade from 2019.1.x to 2019.1.21
- Upgrade from 2018.1.x to 2019.1
- Upgrade from ScyllaDB Open Source 3.0 to ScyllaDB 2019.1
- Submit a ticket
Issue fixed in 2019.1.21 with open source references where available:
- Stability: Unexpected partition key when repairing with different number of shards may resulting in error similar to: “
WARN 2020-11-04 19:06:41,168 [shard 1] repair - repair_writer: keyspace=ks, table=cf, multishard_writer failed: invalid_mutation_fragment_stream
” This error may occur when running repair between nodes with a different core number. #7552 Seastar #867 - Tools: Nodetool tablestats reports inconsistent bloom filter size #4513
10 Mar 2021