KiviDB 1.2.1 release notes

What changed in KiviDB 1.2.1: the new commands, fixes and performance work in this release of the KiviDB server.

KiviDB is open source. v1.2.2 is out. Release notes · Download KiviDB Pricing Sign inStart free Back to Downloads Release version

Release notes

KiviDB v1.2.1

Released November 12, 2026 · Engine changes

1.2.1 is a patch release of 1.2.0. It fixes the 1.2.0 known issues of reshards that could lose writes and replicas that could stop while they saved, and many smaller ways in which a replica, the append-only file or a reshard could end up with other data than the master. It is faster where 1.2.0 was slow, reads Valkey 9 files, and treats keys as bytes, as Redis does. Some commands now answer as Redis does, so read Before you upgrade, and upgrade replicas first.

Download v1.2.1

Highlights

  • A reshard under load no longer loses acknowledged writes, with MIGRATE or CLUSTER MIGRATION IMPORT
  • A replica no longer stops for good while it saves or is promoted; replicas and the AOF stay in step with the master
  • appendfsync always syncs each write before it is acknowledged
  • INFO no longer stalls writes on a server with millions of keys that have a TTL
  • Reads Valkey 9.0 and 9.1 RDB files; Dragonfly, KeyDB and Redis Stack 6.2 files load
  • HELLO reports server: redis, so redis-py and Jedis turn on client-side caching
  • Signed apt and dnf repositories at packages.kividb.io, and cargo install kividb

Clusters

Reshards keep every acknowledged write

A reshard under load, with MIGRATE (redis-cli --cluster reshard) or with CLUSTER MIGRATION IMPORT (the Kubernetes operator), no longer loses acknowledged writes: a write checks whether its keys have left the node and is redirected if they have. A failover of the source during an atomic slot migration no longer loses the writes the new master acknowledged, and a drained node no longer deletes the keys it moved.

Replication and durability

Replicas and the AOF stay in step with the master

A replica no longer stops for good while it saves or is promoted. CLIENT PAUSE ... WRITE replies only once every write already being applied is in the offset, so a switchover no longer promotes a replica without the last acknowledged write. Expired keys and hash fields are removed by the master and sent on, so a replica no longer keeps what the master no longer has, and a replica that falls behind no longer makes its master evict keys and refuse writes.

appendfsync always now syncs each write to disk before it is acknowledged; it was accepted and did nothing. A log that is not replayed is never deleted, and a snapshot that is not whole is refused instead of loaded in part.

Speed and compatibility

Faster where 1.2.0 was slow

INFO takes about 0.1 ms with 5 million keys that have a TTL, against 55 ms, and an idle server with such keys no longer spends CPU on them. HSET no longer takes a shared lock when no search index is defined, and ZREM, ZCOUNT and ZREMRANGEBYSCORE no longer scan the whole sorted set.

Moving data in, and keys as bytes

KiviDB reads Valkey 9.0 and 9.1 RDB files and replicates from a Valkey 9 primary; Dragonfly's hashes with field TTLs and JSON, KeyDB's field TTLs and Redis Stack 6.2 files load. Every command takes a key that is not UTF-8, as Redis does.

Upgrading

Take a backup, then upgrade replicas first and their master after: 1.2.1 can write what 1.2.0 cannot read. Check the Before you upgrade list in the release notes on GitHub first: ACL categories are Redis's (a user with +@write but not +@connection can no longer SELECT, and one with +@read but not +@connection can no longer WAIT), WAIT with no replicas waits out its timeout, HELLO says server: redis, and GEORADIUS is refused on a read-only replica. Run BGREWRITEAOF once after upgrading from 1.2.0. On KiviDB Cloud, new databases start on 1.2.1, and databases on 1.2.0 are moved to it in their maintenance window, replicas first, with 48 hours' notice.

Go to Downloads Newer: v1.2.2Older: v1.2.0 KiviDB

A Redis-compatible in-memory database, written in Rust. Run it yourself or on KiviDB Cloud.

Product

Use cases

Compare

Developers

Company

Legal

© 2026 KIVIDB PRIVATE LIMITED CIN: U62011MP2026PTC083420 · GSTIN: 23AAMCK7754Q1ZO Indore, Madhya Pradesh, India

Redis® is a registered trademark of Redis Ltd. Dragonfly™ is a trademark of DragonflyDB Technologies Ltd. Valkey is a trademark of LF Projects, LLC. KiviDB is not affiliated with or endorsed by any of them. NVIDIA and NVIDIA Inception are trademarks of NVIDIA Corporation. All other trademarks are the property of their respective owners.