[RELEASE] ScyllaDB 5.4.2

The ScyllaDB team announces ScyllaDB Open Source 5.4.2, a bugfix release of the ScyllaDB 5.4 stable branch. ScyllaDB Open Source 5.4.2, like all past and future 5.x.y releases, is backward compatible and supports rolling upgrades.

Users are encouraged to upgrade to 5.4.2.

Related links:

Issue fixed in this release:

  • 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: 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
  • Stability: compaction_manager::perform_cleanup does not handle condition_variable_timed_out, than may cause nodetool cleanup to fails with exit status 2. #15669
  • Stability: nodes crashing during repair operations (due to no reader-closing on unexpected exception) #16606
  • Stability: tasks: dangling reference to task’s child pointer #16380
  • Stability: tombstone might not be garbage-collected due to conflicts with data in commitlog. #15777
  • Correctness: a very rare bug in row cache might return a wrong value #15483
  • 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
  • Java Tools: update “guava” package to 32.1.3-jre scylla-tools-java#365
  • Java Tools: Upgrade scylla-driver-core from to scylla-tools-java#343
  • Java tools: Use newer hk2-locator in order to get rid of javassist scylla-jmx#231
  • Tools: scylla nodetool crashes if invoked without further args #16451
  • Tools: scylla-sstable tool crash due to unclosed reader in tools/schema_loader.cc #16519

Does this include the fix for this issue:


No. the commit is backported to 5.4 and will be part of the next 5.4 patch release (5.4.3)