The ScyllaDB team announces ScyllaDB Open Source 4.3.2, a bugfix release of the ScyllaDB 4.3 stable branch.
ScyllaDB Open Source 4.3.2, like all past and future 4.x.y releases, is backward compatible and supports rolling upgrades.
Related links:
- ScyllaDB Open Source 4.3
- Get ScyllaDB Open Source – AWS AMI, Docker, binary packages
- Upgrade from ScyllaDB Open Source 4.x.y to ScyllaDB Open Source 4.x.z
- Upgrade from ScyllaDB Open Source 4.2.x to 4.3.y
- Please let us know if you encounter any problems.
Issues fixed in this release:
- Alternator: unexpected ValidationException in ConditionExpression and FilterExpression #8043
- Alternator: UpdateItem’s “ADD” can’t create a new set or number #7763
- CDC: Limit size of topology description #8048
- Monitoring: False 1 second latency reported in I/O queue delay metrics #8166
- 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_rows
table. If such a large cell was part of a static rows, ScyllaDB would crash #6780 - 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 - ScyllaDB on GCE:
scylla_io_setup
did not configure pre tuned gce instances correctly #7341 - ScyllaDB on AWS: When
psutil.disk_paritions()
reports/ is /dev/root
,aws_instance
mistakenly reports root partition is part of ephemeral disks, and RAID construction will fail. #8055 - Stability:
stream_session::prepare
is missing a string format argument #8067 - Stability: TWCS reshape was silently ignoring windows which contain at least
min_threshold
sstables (can happen with data segregation). #8147
08 Mar 2021