# \[RELEASE\] ScyllaDB 5.4.7

**URL:** <https://forum.scylladb.com/t/release-scylladb-5-4-7/2153>\
**Category:** Release Notes\
**Tags:** open-source, open-source-release, open-source-5-4\
**Created:** [June 10, 2024, 9:43am UTC](https://forum.scylladb.com/t/release-scylladb-5-4-7/2153 "2024-06-10T09:43:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tzach](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/tzach/32/172_2.png) [@tzach](https://forum.scylladb.com/u/tzach)\
**Post date:** [June 10, 2024, 9:43am UTC](https://forum.scylladb.com/t/release-scylladb-5-4-7/2153/1 "2024-06-10T09:43:10Z")

</div>

The ScyllaDB team announces ScyllaDB Open Source 5.4.7, a bugfix release of the ScyllaDB [5.4](https://forum.scylladb.com/t/release-scylladb-5-4-0-part-1/1084) stable branch. ScyllaDB Open Source 5.4.7, like all past and future 5.x.y releases, is backward compatible and supports [rolling upgrades](https://docs.scylladb.com/upgrade/upgrade-opensource/upgrade-guide-from-5.x.y-to-5.x.z/).

Note that the latest ScyllaDB Open Source stable release is [6.0](https://forum.scylladb.com/t/release-scylladb-6-0/2143) and you are encouraged to upgrade to it.

Related links:

- [ScyllaDB Open Source 5.4.0](https://forum.scylladb.com/t/release-scylladb-5-4-0-part-1/1084)
- [Get ScyllaDB Open Source](https://www.scylladb.com/download/open-source/) - AWS AMI, GCP Docker, binary packages and unified installer
- [ScyllaDB Web Installer for Linux](https://docs.scylladb.com/stable/getting-started/install-scylla/scylla-web-installer.html) (all releases)
- [Upgrade from ScyllaDB Open Source 5.x.y to Scylla Open Source 5.x.z](https://docs.scylladb.com/upgrade/upgrade-opensource/upgrade-guide-from-5.x.y-to-5.x.z/)
- [Upgrade from ScyllaDB Open Source 5.2.x to 5.4.y](https://opensource.docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-5.2-to-5.4/index.html)
- Please[let us know](https://github.com/scylladb/scylla/issues) if you encounter an issue.

Issue fixed in this release:

- Tracing: the ability of figuring which shard owns a partition from system.large\_partition by analyzing a corresponding sstable id was broken when moving to UUID based SSTable numbering [#18381](https://github.com/scylladb/scylladb/issues/18381)  
Instead, one can use [scylla sstable shard-of](https://opensource.docs.scylladb.com/master/operating-scylla/admin-tools/scylla-sstable.html#shard-of) to extract shards which own the specified SSTables. [#16343](https://github.com/scylladb/scylladb/issues/16343)

- Stability: Bad estimation for temporary sstables (containing GCed data only) causes, in the worst case, of 2x space amplification for filters [#18283](https://github.com/scylladb/scylladb/issues/18283)

- Stability: clustering\_range intersection() can cause an infinite loop [#18688](https://github.com/scylladb/scylladb/issues/18688)

- Image: while dropping openssh-server from the ScyllaDB image, other system packages used by ScyllaDB scripts were also dropped.[#17787](https://github.com/scylladb/scylladb/issues/17787) The regression was introduced in 5.4.6.

- Config: default [task\_ttl\_in\_seconds](https://opensource.docs.scylladb.com/master/reference/configuration-parameters.html#confval-task_ttl_in_seconds) is 0, but scylla.yaml changes the value to 10. [#16714](https://github.com/scylladb/scylladb/issues/16714)

- Stability: direct failure detector: make ping timeout configurable and increase the default, from 300 to 600 ms [#16607](https://github.com/scylladb/scylladb/issues/16607). Failure detector is an internal inter-node mechanism.

- Stability: fromJson() or INSERT JSON fails to set a map\<timeuuid, int\> [#18477](https://github.com/scylladb/scylladb/issues/18477)

- Stability: handle\_paxos\_accept() fails to record a trace message when done with handling [#18725](https://github.com/scylladb/scylladb/issues/18725)

- Stability: mutation\_fragment\_stream\_validating\_filter doesn’t respect validation\_level::none [#18662](https://github.com/scylladb/scylladb/issues/18662). The issue might cause false-positive validation errors during repair/streaming, leading to aborting the operation.

- Stability: Materialized View (MV): memory used by a view updates batch is incorrectly divided [#17854](https://github.com/scylladb/scylladb/issues/17854)

- Stability: MV semaphore units are not kept alive until a view update finishes [#17890](https://github.com/scylladb/scylladb/issues/17890)

- Tooling: native sstable validation yields false positive errors (limited to MX format) [#16326](https://github.com/scylladb/scylladb/issues/16326)

- Stability: Potential use-after-move in streaming’s stream\_result\_future (courtesy of clang-tidy) [#18332](https://github.com/scylladb/scylladb/issues/18332)

- Stability: Reclaimed bloom filter is left back in disk when the SSTable is deleted [#18398](https://github.com/scylladb/scylladb/issues/18398)

- repair: add control for repair percentage for partition count estimation [#18615](https://github.com/scylladb/scylladb/issues/18615). The new parameter is [repair\_partition\_count\_estimation\_ratio](https://opensource.docs.scylladb.com/stable/reference/configuration-parameters.html#confval-repair_partition_count_estimation_ratio). The default 10% has not changed.

- Stability: Scylla crash when reading from mutation fragments with token() filtering [#18637](https://github.com/scylladb/scylladb/issues/18637)

- Performance: The algorithm for picking an index for a request is not always deterministic [#7969](https://github.com/scylladb/scylladb/issues/7969)

- Stability: Use-after-move in sstable writer (courtesy of clang-tidy) [#18323](https://github.com/scylladb/scylladb/issues/18323)

- Stability: Use-after-move in thrift/handler.cc:make\_non\_overlapping\_ranges() (courtesy of clang-tidy) [#18356](https://github.com/scylladb/scylladb/issues/18356)

- Stability: utils::chunked\_vector fill constructor is exception unsafe [#18635](https://github.com/scylladb/scylladb/issues/18635)

- Stability: Wrong exception is printed in build step exception handling [#18423](https://github.com/scylladb/scylladb/issues/18423)
