Allow to read from master/slave/nearest node when using Redis Standalone/Sentinel #125
Labels
type: feature
A new feature
Milestone
Comments
|
As this feature is experimental it's going to be part of 4.1 and located within an experimental/master-slave package. |
mp911de
added a commit
that referenced
this issue
Nov 11, 2015
This commit adds the API for master-slave setups featuring topology discovery and selecting the source for read operations (read from slave/master/nearest node). The change can improve the usage of slave nodes within a setup and requires no longer multiple connections managed by user code but the connection management is built into the client.
mp911de
added a commit
that referenced
this issue
Nov 24, 2015
This commit adds the API for master-slave setups featuring topology discovery and selecting the source for read operations (read from slave/master/nearest node). The change can improve the usage of slave nodes within a setup and requires no longer multiple connections managed by user code but the connection management is built into the client.
|
Implemented. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Allow to specify routing from where to read data from when using Redis Standalone/Redis Sentinel.
Motivation: Users want to use a master/slave replication setup to use one instance for writes and the other one for writes. While a read-from-slave approach works on a static setup basis, slave connections stick to the same connection points when reconnecting. lettuce does not utilize the full range of nodes when reconnecting. When using Redis Sentinel, slaves can be promoted to masters, so a static setup is not possible. #114 introduces eventual consistency reads within Redis Cluster.
Benefits:
INFO REPLICATIONorSENTINEL SLAVES)The text was updated successfully, but these errors were encountered: