[RELEASE] ScyllaDB Enterprise 2023.1.4

The ScyllaDB team announces ScyllaDB Enterprise 2023.1.4, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2023.1 LTS Release.

2023.1.4 patch release includes multiple minor bug fixes.

You are encouraged to upgrade to it in coordination with the ScyllaDB Support team.

Related Links

The following issues are fixed in this release (with an open-source reference, if available):

  • CQL: Adding (using ALTER TYPE) a UDT field of type Duration doesn’t check whether it’s allowed. For example values of the duration type is not allowed for clustering columns #12913
  • CQL: validation of cql create statement options should happen when it is created, not when executed #14710.
  • Alternator: possible race between concurrent TagResource from multiple nodes #6389
  • Performance: ICS is not honoring tombstone GC mode when scheduling compaction jobs, which may lead to a less efficient compaction scheduling.
  • Performance: high latency in multi-partition scans #14008
  • Performance: Bloom filter efficiency can be reduced after node operation. When writing an sstable, ScyllaDB estimates how many partitions it will have in order to size the bloom filter correctly. In some cases, the estimation was suboptimal for TWCS. #15704
  • Stability: a bug in calculates the duration that it takes to replenish the specified amount of tokens, which can cause compaction overload after upgrade seastar#1722
  • Stability: Inefficient memory footprint of topology::compare_endpoints might cause a restart when a node join the cluster
  • Stability: cdc::topology_description: avoid large allocation #15302
  • Stability: assertion when, as a result of a failure, a RPC for a snapshot is sent before a previous snapshot request was handled. #15222
  • Stability: gossiper: mark_alive: _pending_mark_alive_endpoints is not cleared on exception paths #14839
  • Stability: gossiper::mark_alive leaves a stray background job behind #14791
  • Stability: The hints synchronization point REST API allows waiting for hints to replay. Misuse of the API cookie could lead to unbounded memory usage #9405
  • Stability: a race condition may lead to a wrong schema version in system.peers when using raft #15078
  • Stability: commitlog replay can cause abort due to over-extended skip. During commitlog replay, ScyllaDB skips over corrupted sections. However if the corrupted section also has corrupt size, it can lead to a crash. #15269
  • Tools: scylla-sstable ignores scylla.yaml unless it is explicitly provided #16132
  • Tools: scylla-sstable cryptic errors printed when table is not found in schema-tables #16459
  • Tools: scylla-sstable: schema_loader uses dummy db::config when loading schema #16480
  • Tools: scylla-sstable tool crash due to unclosed reader in tools/schema_loader.cc #16519
  • Java Tools: Upgrade scylla-driver-core from to scylla-tools-java#343
  • Java Tools: update “guava” package to 32.1.3-jre scylla-tools-java#365
  • Java Tools: Old version of libthrift and others dependency scylla-tools-java#352
  • Java tools: Use newer hk2-locator in order to get rid of javassist scylla-jmx#231
  • Java Tools: nodetool fails due to tderr: error: ‘java.lang.Object com.google.common.base.Objects.firstNonNull(java.lang.Object, java.lang.Object)’. Root cause is a 3rd party package, io.airlift.airline, API update,scylla-tools-java#374
  • Setup: dist: ‘ordering cycle’ on var-lib-scylla.mount might be wrong, resulting in a potential wrong init order of dependencies, like file system and scylla service booth. #8761
  • UX: Wrong shard id is used in shard_repair_task_impl, leading to a wrong log message #12955