The ScyllaDB team announces the release of ScyllaDB Enterprise 2020.1.7, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2020.1. As always, ScyllaDB Enterprise customers are encouraged to upgrade to ScyllaDB Enterprise 2020.1.7 in coordination with the ScyllaDB support team.
Full list of stability improvements and bug fixes below.
Related Links
- Get ScyllaDB 2020.1.7 (customers only, or 30-day evaluation)
- Upgrade from 2019.1.x to 2020.1.7
- Upgrade from ScyllaDB Open Source 4.0 to ScyllaDB 2020.1
- Submit a ticket
Fixed issues in this release are listed below, with open source references, if present:
- CQL: Invalid aggregation result on table with index: When using aggregates
(COUNT(*))on table with index on clustering key and filtering on clustering key, wrong results are returned #7355 - CQL: CQL prepared statements incomplete support for “unset” values #7740
- CQL: Restrictions missing support for “IN” on tables with collections, added in Cassandra 4.0 #7743 #4251
- CQL: Requests Role or User are now tracked in the tracing output #6737
- Tools: Nodetool tablestats reports inconsistent bloom filter size #4513
- Tools: Empty partition keys make nodes unbootable #6106
- Stability: Commit log performance regression introduced in 2020.1.0 had the unfortunate side effect with
O_DSYNC: each 128k writes also needs to flush the XFS log. - 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 - Stability: upgrade which include system schema changes may fail. For example from 2019.1 to 2020.1.
- Stability: A materialized view update of a large partition may cause large allocation which can cause an endless view update apply attempt → failure → retry loop
- Stability: Fix cross-shard sharing of
schema_ptrpotentially leading to use-after-free of schema #7535 - Stability: ‘ascii’ type column isn’t validated, and one could create illegal ascii values by using CQL without bind variables #5421
- Stability: ScyllaDB records large data cells in the
system.large_rowstable. If such a large cell was part of a static rows, ScyllaDB would crash #6780 - Stability: Hinted handoff is using very long timeout to sending some hints #7051
- Stability: materialized view builder: ScyllaDB stuck on stopping #7077
- Stability: a rare race condition may cause TWCS sometimes stops dropping expired SSTables #8038
ScyllaDB on AWS: Whenpsutil.disk_paritions()reports/ is /dev/root,aws_instancemistakenly reports root partition is part of ephemeral disks, and RAID construction will fail. #8055 - Stability:
stream_session::prepareis missing a string format argument #8067 - Monitoring: False 1 second latency reported in I/O queue delay metrics #8166
09 Mar 2021
