Page History

...

The current implementation is not thread-safe and displays many concurrency issues when multiple clients are operating on the same keys or data structures. (Since the Redis API and data structures do not map directly to Geode APIs and data structures, the API implementation must perform a certain amount of translation and accounting, which have not been implemented in a thread-safe manner before.) Additionally, the data is not stored in a manner that can provide High Availability - data is not distributed among multiple serves servers so a single failure can lose data.

...

To further ensure HA, the partition type of the internal Redis regions will no longer default to PARTITION, and will no longer be customizable and . It will be fixed as a to the PARTITION_REDUNDANT type, with the default redundancy of 1.

Note that the complexity of reconnecting to a new server can be minimized with a load balancer or DNS aliases. If a list of healthy servers is kept, clients can be directed to individual servers via the normal DNS lookup process. If the server a client is connected to fails, the client will try to reconnect to the same host, and the DNS alias will automatically direct that client to a healthy server. From the client’s perspective, it will look like a momentary network failure, and no special failover logic is necessary.

...