The current implementation of the Redis ring does not support specifying custom shard health check rules.
We use a Redis shard to distribute the load across multiple Redis slave instances.
However, if any shard encounters replication issues, the Redis ring continues to utilize this shard because it responds to ping requests successfully.
Thus, the Redis ring does not remove the malfunctioning shard, even though it is inconsistent.
This pull request proposes adding a HeartbeatFn option to the RingOptions, which can be configured during ring construction. This addition enables the definition of custom health check logic, such as checks based on the current replication status of the shard.
The current implementation of the Redis ring does not support specifying custom shard health check rules. We use a Redis shard to distribute the load across multiple Redis slave instances. However, if any shard encounters replication issues, the Redis ring continues to utilize this shard because it responds to ping requests successfully. Thus, the Redis ring does not remove the malfunctioning shard, even though it is inconsistent.
This pull request proposes adding a HeartbeatFn option to the RingOptions, which can be configured during ring construction. This addition enables the definition of custom health check logic, such as checks based on the current replication status of the shard.