[RELEASE] Scylla 4.3.6, Scylla 4.3.5

9 views
Skip to first unread message

Tzach Livyatan

unread,
Aug 10, 2021, 2:54:04 PMAug 10
to ScyllaDB users, scylladb-dev

The ScyllaDB team announces Scylla Open Source 4.3.6, a bugfix release of the Scylla 4.3 stable branch.

Scylla Open Source 4.3.6, like all past and future 4.x.y releases, is backward compatible and supports rolling upgrades.

Please note the latest stable release of Scylla is 4.4.


Also below are issues fixed in release 4.3.5, promoted on June 20, and I failed to announce.


Related links:


Issues fixed in Scylla 4.3.6 release

  • API uses incorrect plus<int> to sum up cf.active_memtable().partition_count(), which can result with  the value wrapped around if bigger than 2^32.  #9090

  • Stability: Scylla aborts with error “./seastar/src/core/fstream.cc:172: virtual seastar::file_data_source_impl::~file_data_source_impl(): Assertion `_reads_in_progress == 0' failed” when sstable mutation reader is fast forwarding #9049

  • Stability: repair does not consider memory bloat which may cause repair to use more memory and cause std::bad_alloc. #8641

  • Stability: When scylla-server was stopped manually, a few minutes later, the scylla-fstrim service started it again #8921

  • Tools: Nodetool cleanup failed because of "DC or rack not found in snitch properties" #7930

  • Stability: Some of appending_hash<> instantiations have throwing operator() #8983

  • Stability: Reshape may ignore overlapping in level L where L > 0 #8531

  • Performance: Significant write amplification when reshaping level 0 in a LCS table #8345


Issues fixed in Scylla 4.3.5 release

  • Stability: cdc: log: use-after-free in process_bytes_visitor #8117

  • Install: scylla_coredump_setup fails when on an environment with hard limit of coredump is set to zero, like Oracle Linux 8.1  #8238

  • Log: Incomplete information logged when std::nested_exception is printed #8327

  • Install: scylla_io_setup failed with error: seastar - Could not setup Async I/O on aws instances (r5, r5b) and gp3 ebs volumes #8587

  • Stability: Certain combination of filtering, index, and frozen collection, causes "marshalling error" failure #7888

  • Alternator: nodetool cannot work on a table with a dot in its name #6521

  • Alternator: ConditionExpression wrong comparison of two non-existent attributes #8511

  • Alternator: incorrect inequality check of two sets #8513

  • Alternator - incorrect set equality comparison inside a nested document #8514


Regards
Tzach
Reply all
Reply to author
Forward
0 new messages