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
The documentation says NOT to use multiple connections for redis instances in the same cluster, but we have a use case where we must write to a master (obviously) in one data center while making sure "reads" go to a different data center, but both instances belong to the same cluster name.
To address this, we set up F5 with virtual host names with rules using webdis "/info" to find the master for writing, and the nearest redis instance for reading. We configure the application using the virtual host names like this:
The documentation says NOT to use multiple connections for redis instances in the same cluster, but we have a use case where we must write to a master (obviously) in one data center while making sure "reads" go to a different data center, but both instances belong to the same cluster name.
To address this, we set up F5 with virtual host names with rules using webdis "/info" to find the master for writing, and the nearest redis instance for reading. We configure the application using the virtual host names like this:
Is this a valid configuration? It seems to work fine, although we have not performed serious testing on it.
The text was updated successfully, but these errors were encountered: