Repository navigation
v0.9.7
Valkey becomes the recommended backend, newer Redis and Valkey commands are supported, and two replication and read repair bugs are fixed.
Upgrade notes
- SUNIONSTORE, ZINTERSTORE, ZUNIONSTORE, and SORT and GEORADIUS(BYMEMBER) with STORE or STOREDIST are writes now: they run in every rack and DC under the write consistency level. Before, Dynomite took them for reads, so the result was stored only in the local rack (DC_ONE) or the local DC (quorum levels); copies of those destination keys elsewhere may be stale or missing from before the upgrade. TTL is a read now, like PTTL.
- ECHO goes to the local datastore, like PING, instead of getting the unknown command error.
- Commands that only newer datastores have (see below) are passed on, and a datastore without one refuses it. Upgrade all of a cluster's datastores before using such a command, or a write runs on some replicas and is refused on others.
Backends
- Valkey is now the recommended and default-tested backend; Redis stays fully supported through the same protocol (RESP,
data_store: 0), and the example configurations work with either. See the README's new Backends section for why (Redis is no longer BSD-licensed since 2024). - CI runs the functional tests against the latest Valkey and Redis releases (9.1.3 and 8.10.3) and Debian trixie's packages (Valkey 8.1.1, Redis 8.0.2).
New commands
- Hash field expiry (Redis 7.4 and 8, Valkey 9): HSETEX, HGETEX, HGETDEL, HEXPIRE, HPEXPIRE, HEXPIREAT, HPEXPIREAT, HPERSIST, HTTL, HPTTL, HEXPIRETIME, HPEXPIRETIME.
- DELIFEQ (Valkey 9) and ECHO.
- GETEX, GETDEL, EXPIRETIME, PEXPIRETIME, LPOS, SMISMEMBER, ZMSCORE, ZPOPMIN, ZPOPMAX.
- GETEX and HGETEX are always writes, since they can change TTLs. ZPOPMIN and ZPOPMAX pop the same members on every replica, so unlike SPOP they work with any number of racks. Read repairs don't cover the new commands. notes/redis.md has the details, including replies in milliseconds that can differ between replicas after a relative TTL.
Fixes
- The results of the commands listed in the upgrade notes are replicated to every rack and DC.
- With read repairs enabled, SELECT, SCRIPT EXISTS/FLUSH/KILL, CLIENT SETINFO, HELLO, DBSIZE and
dyno_configread past the end of an internal table, and whatever followed it decided whether the request was rewritten for read repair.
Testing
- The functional tests run on Valkey or Redis (
DYN_TEST_SERVERpicks the server binary) and print which one they use. - New functional tests for the stored results, the new commands, and the read repair table; the parser unit tests also check whether a request is taken for a read or a write.
- A failing functional test job in CI prints the end of every node's log and uploads the full logs as an artifact.
Full Changelog: v0.9.6...v0.9.7