KeyDB development status

Hello,

Can please someone provide more information about KeyDB development status.

1. There are lot of reports about crashes
2. There a lot of reports about sync issues in Multi-Master configuration
3. Packages for Ubuntu 22.04 are missing since May of 2022
4. Redis is already v7 with a new RDB format which is incompatible with KeyDB v6
5. What is about Roadmap - What is on the Roadmap for the KeyDB Project?
6. There was a news in blog, May 11, 2022 - KeyDB (YC S20) Joins Snap.

Thank you!

[Diz-X]

There are a lot of fixes in coming releases as far as I know, problem is they haven't released the binary releases yet for the past 6+ months. Only thing you can do is go back to older version or compile your own version... I hope they will be doing a new binary release soon..

[silviucpp]

Will be nice if they can go over the issue tracker and comment to the issues that were addressed in the coming release. As there are tons of commits.

[DreadfulCode]

KeyDB 6.2.2 is the only stable production ready version, as far as I know.

Can confirm: 6.3.1 inexplicably crashes with multi-master on. When ran as a systemd process, everything will appear green, when things are really red.

[fannyfan414]

@msotheeswaran @JohnSully any news for new releases?

[msotheeswaran-sc]

We are working on a release for this coming week, which will include debian 12 and ubuntu 22.04 packaging.
I will be working on further crash fixes after the release is out.
@JohnSully has been working on a new proxy server for KeyDB which he will be able to talk about soon along with a further roadmap

Tentative 6.3.2 Release notes:

• Added new soft shutdown feature, can be enabled with config "soft-shutdown yes".
  If soft shutdown is enabled, instead of shutting down right away, the server will wait until all clients have disconnected, and will reject all new connection attempts.
• Fixed memory leak with tls certificates when tls allowlist is enabled
• Fixed bug in rdb load with flash enabled to ensure all dbs are safe to load (previously only checked db[0])
• Fixed race conditions in rdb load and replication
• Fixed memory access of rdb file after it should have been deleted
• Fixed integer overflow bug in flash(Issue [CRASH] command Keys * crashed the server when there are more than 10 GB of cached data #486)
• Improve TLS latency by queueing new commands before executing instead of after
• Removed O(n) count of memory usage from info command(replaced by O(1) estimate)
• Improved latency of clearing large number of flash DBs(Thanks to Paul Chen for this fix)(Issue [BUG] flushall async took 60 seconds in flash use case when the redis.conf configures 256 databases #516)
• replaced sprintf with snprintf to avoid potential security bugs
• Fixed bug where a failed move due to key already existing in move target would result in the key being removed from move source(Thanks to Paul Chen for this fix)(Issue [BUG] Moves key to another DB, the source key was removed if the move failed due to the key exists in the destination db #497)
• Fixed usage of deprecated OpenSSL api in OpenSSL v>3.0.1(Issue with openssl 3.0.1 have problem #392)
  Other fixed issues: [BUG] running cli "HKEYS" without passing parameter when enabling teststorageprovider will crash KeyDB server #480 [CRASH] The server crashed when resizing the replication backlog size and running info at the same time #477 Patch src/replication.cpp to support FreeBSD (remove O_LARGEFILE in open(), like Apple/MacOS) #454 [CRASH] Lua SCAN with COUNT 100 #452

[Skaronator]

The development seems to be halted again. At least that my outside observation as someone who is interested in KeyDB.

Last release was over a year ago. Last news on the website was over a year ago.

https://valkey.io/about

Valkey is an open source continuation of Redis, created in March 2024 following Redis's shift to a non-open source license. This initiative was led by Madelyn Olson, a notable figure in the Redis community and a former core maintainer at AWS, along with other contributors who sought to preserve the original open source ethos of Redis. The transition garnered substantial backing from leading tech corporations including AWS, Google, Oracle, Ericsson, and Snap, with the Linux Foundation stepping in to provide a stable platform for this new direction. Amidst the landscape of Redis alternatives, Valkey stands out with strong support from cloud services providers, positioning it as a promising solution for future open source database needs.

It miss some KeyDB features, but do we have now any other alternatives?