Mordern Redis Cluster solution for easy operation.
Undermoonis a self-managed Redis clustering system based on Redis Cluster Protocol supporting:
Any storage system implementing redis protocol could also somehow work with undermoon, such as KeyDB.
For more in-depth explanation of Redis Cluster Protocol and how Undermoon implement it, please refer to Redis Cluster Protocol.
Metadata storage stores all the metadata of the whole
undermooncluster, including existing Redis instances, proxies, and exposed Redis clusters. Now it's an in-memory storage server called
Memory Broker. When using undermoon-operator, this
Memory Brokerwill change to use
ConfigMapto store the data.
Coordinator will synchronize the metadata between broker and server proxy. It also actively checks the liveness of server proxy and initiates failover.
The storage cluster consists of server proxies and Redis instances. It serves just like the official Redis Cluster to the applications. A Redis Cluster Proxy could be added between it and applications so that applications don't need to upgrade their Redis clients to smart clients.
Chunk is the smallest building block of every single exposed Redis Cluster. Each chunk consists of 4 Redis instances and 2 server proxies evenly distributed in two different physical machines. So the node number of each Redis cluster will be the multiples of 4 with half masters and half replicas.
The design of chunk makes it very easy to build a cluster with a good topology for workload balancing.
Using undermoon-operator is the easiest way to create Redis clusters if you have Kubernetes.
helm install my-undermoon-operator undermoon-operator-.tgz
README.mdof undermoon-operator for how to use it.
Or you can set them up without docker following this docs: setting up undermoon manually.
undermoontries to avoid
unsafeand some calls that could crash like
Run the following commands before committing your codes:
$ make lint $ make test
See more in the development guide.