OpsForGeo producing "READONLY You can't write against a read only replica" on READS... only if master & replica configured #1813
Labels
status: good-first-issue
An issue that can only be worked on by brand new contributors
type: feature
A new feature
Milestone
Bug Report
This is a strange one and something that is causing us to depend on a single master cache instance for both our reads and our writes.
Current Behavior
When we configure Lettuce with the configuration below, we see it produce the following stacktrace when we perform a read operation using:
If we only configure a single master instance using
RedisStandaloneConfiguration
we do not see this issue at all.Stack trace
Input Code
Configuration
Expected behavior/code
Should produce an empty/non-empty results object.
Environment
Additional context
If you break point in the code and execute the
radius()
command numerous times within the same process, it fails every few times. If, however, you execute it via a REST endpoint, it will fail every time.The text was updated successfully, but these errors were encountered: