[RELEASE] Scylla 4.5 RC6

36 views
Skip to first unread message

Tzach Livyatan

<tzach@scylladb.com>
unread,
Aug 23, 2021, 12:59:38 PM8/23/21
to ScyllaDB users, scylladb-dev

The Scylla team is pleased to announce Scylla Open Source 4.5 rc6, a Release Candidate for the Scylla Open Source 4.5 minor release.

Use the release candidate with caution; rc6 is not production-ready yet. You can help stabilize Scylla Open Source 4.5 by reporting bugs here.


Please note that only the last two minor releases of Scylla Open Source project are supported. Once Scylla Open Source 4.5 is officially released, only Scylla Open Source 4.5 and Scylla 4.4 will be supported, and Scylla 4.3 will be retired.


For a complete description of Scylla 4.5 new features and bug fixes, see Scylla 4.5 RC1


Related Links     

* Scylla 4.5 RC1 , RC2, RC3, RC4, RC5

* Get Scylla Open Source 4.5 release candidate (at the bottom of the under “Select Version” list) 

* Report a problem


Updates and bug fixes since 4.5 RC5

  • A new config “commitlog_use_hard_size_limit" sets whether or not to use a hard size limit for commitlog disk usage. Default is false. Enabling this can cause latency spikes, whereas the default can lead to occasional disk usage peaks as seen in #9053

  • Upscale (adding cores): On some environments /sys/devices/system/cpu/cpufreq/policy0/scaling_governor does not exist even if it supported CPU scaling. Instead, /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is used.  #9191

  • Stability: load-and-stream fails: Assertion `!sst->is_shared()' failed and aborting on shard.  #9173

  • Stability: excessive compaction of a fully expired TWCS table when running repair #8710

  • API uses incorrect plus<int> to sum up cf.active_memtable().partition_count(), which can result with  

  • CQL: Creating a table that looks like a secondary index breaks the secondary index creation mechanism #8620. This fix accidentally broke CREATE INDEX IF NOT EXISTS #8717

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


Regards
Tzach
Reply all
Reply to author
Forward
0 new messages