# \[RELEASE\] ScyllaDB 5.2.15

**URL:** <https://forum.scylladb.com/t/release-scylladb-5-2-15/1306>\
**Category:** Release Notes\
**Tags:** open-source, open-source-release, open-source-5-2\
**Created:** [February 14, 2024, 4:21pm UTC](https://forum.scylladb.com/t/release-scylladb-5-2-15/1306 "2024-02-14T16:21:45Z")\
**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:** [February 14, 2024, 4:21pm UTC](https://forum.scylladb.com/t/release-scylladb-5-2-15/1306/1 "2024-02-14T16:21:45Z")

</div>

The ScyllaDB team announces ScyllaDB Open Source 5.2.15, a bugfix release of the ScyllaDB [5.2](https://forum.scylladb.com/t/release-scylla-5-2-0-release-part-1/519) stable branch. ScyllaDB Open Source 5.2.15, 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 [5.4](https://forum.scylladb.com/t/release-scylladb-5-4-0-part-1/1084/4) and you are encouraged to upgrade to it.

Related links:

- [ScyllaDB Open Source 5.2](https://forum.scylladb.com/t/release-scylla-5-2-0-release-part-1/519)
- [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.1.x to 5.2.y](https://docs.scylladb.com/stable/upgrade/upgrade-opensource/upgrade-guide-from-5.1-to-5.2/index.html)
- Please[let us know](https://github.com/scylladb/scylla/issues) if you encounter an issue.

Issue fixed in this release:

- CQL: Server-side DESCRIBE should include scylladb-specific options like paxos\_grace\_seconds, and tombstone\_gc [#12389](https://github.com/scylladb/scylladb/issues/12389)

- Correctness: Inserted data only becomes available after restart. The root cause is a very rare bug in the cache, which is hidden (in most cases) by replication and reconciliation [#16759](https://github.com/scylladb/scylladb/issues/16759). Thanks to user rngcntr for reporting and helping debug it.

- Stability: Adding a column to the base table should invalidate prepared statements for views [#16392](https://github.com/scylladb/scylladb/issues/16392)

- Stability: Bootstrap fails due to inconsistent schema after group0 catch up when table was recreated in the past, in an older version of Scylla [#16683](https://github.com/scylladb/scylladb/issues/16683)

- Stability: database\_test may fail due to ignored exceptional future on table drop [#14971](https://github.com/scylladb/scylladb/issues/14971)

- Stability: nodes crashing during repair operations (due to no reader-closing on unexpected exception) [#16606](https://github.com/scylladb/scylladb/issues/16606)

- Stability: Raft system storage needs to save the snapshot descriptor and truncate the log atomically. [#9603](https://github.com/scylladb/scylladb/issues/9603) The original fix proved to be incomplete.

- Stability: raft: large delays between `io_fiber` iterations in schema change test. [#15622](https://github.com/scylladb/scylladb/issues/15622). ScyllaDB uses two separate memory reservation systems for memtables: user, used for user writes, and system, used for ScyllaDB’s own writes. The root cause was Raft did not use the system reservation.

- Stability: Task manager api responds with Internal Server Error [#14914](https://github.com/scylladb/scylladb/issues/14914)

- Stability: tasks: dangling reference to task’s child pointer [#16380](https://github.com/scylladb/scylladb/issues/16380)

- Stability: When using Raft for topology and schema changes, ScyllaDB does not force the schema and topology to be transferred to new nodes. [#14066](https://github.com/scylladb/scylladb/issues/14066)

- Stability: mintimeuuid() call with large negative timestamps may crash ScyllaDB. [#17035](https://github.com/scylladb/scylladb/issues/17035)

- Setup: scylla\_raid\_setup: faillback to other paths when UUID not available [#13803](https://github.com/scylladb/scylladb/pull/13803)