You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With using READ_ONLY mode and not available master node after first call cluster client returns network err instead of handling commands with available replica.
2 consecutive calls to clusterClient.get("not_existing_key") not existing key from redis-cluster with down master node and available replica differ in result.
Prerequisites redis cluster configured to tolerate not available master and handle requests with replica in READ_ONLY mode.
Expected Behavior
Cluster returns redis:nil for not existing key when READ_ONLY enabled and continue handling requests.
redis-cli -c with READ_ONLY command continue to respond commands with master not available.
Current Behavior
clusterclient return on first get request redis:nil error and on following requests return network error.
Possible Solution
ClusterClient marks node as failing on if ReadOnly is available and cmd returns and error including key not exists(redis:nil).
Possible solution to mark node as failing only on network errors.
Current behavior prevent using clusterclient and handle get requests with failed master node hence redis-cluster stop handling request if any master node not available.
The text was updated successfully, but these errors were encountered:
eskomorokhov
changed the title
Readonly mode set node failing on get not existing key
Readonly mode sets node failing on get not existing key
Jul 19, 2023
With using READ_ONLY mode and not available master node after first call cluster client returns network err instead of handling commands with available replica.
2 consecutive calls to
clusterClient.get("not_existing_key")
not existing key from redis-cluster with down master node and available replica differ in result.Prerequisites redis cluster configured to tolerate not available master and handle requests with replica in READ_ONLY mode.
Expected Behavior
Cluster returns redis:nil for not existing key when READ_ONLY enabled and continue handling requests.
redis-cli -c with READ_ONLY command continue to respond commands with master not available.
Current Behavior
clusterclient return on first
get
request redis:nil error and on following requests return network error.Possible Solution
ClusterClient marks node as failing on if ReadOnly is available and cmd returns and error including key not exists(redis:nil).
Possible solution to mark node as failing only on network errors.
Steps to Reproduce
Context (Environment)
Current behavior prevent using clusterclient and handle get requests with failed master node hence redis-cluster stop handling request if any master node not available.
Detailed Description
Mark node as failing only on network errors
Possible Implementation
The text was updated successfully, but these errors were encountered: