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
I have setup two mcrouters each with the following config: { "pools": { "session": { "servers": [ "10.1.5.100:11211", "10.1.5.102:11211" ] } }, "route": { "type": "OperationSelectorRoute", "operation_policies": { "add": "AllSyncRoute|Pool|session", "delete": "AllSyncRoute|Pool|session", "get": "LatestRoute|Pool|session", "set": "AllSyncRoute|Pool|session" } } }
However, i noticed that when one of then memcache servers goes down, e.g., 10.1.5.100:11211, mcrouter will continue serving from the remaining server 10.1.5.101:11211, but will produce connection errors with attempts to connect to the memcache server that is down.
Is there a way to configure mcrouter so it can stop attempting connecting to the configured memcache server that has gone down?
The text was updated successfully, but these errors were encountered:
I have setup two mcrouters each with the following config:
{ "pools": { "session": { "servers": [ "10.1.5.100:11211", "10.1.5.102:11211" ] } }, "route": { "type": "OperationSelectorRoute", "operation_policies": { "add": "AllSyncRoute|Pool|session", "delete": "AllSyncRoute|Pool|session", "get": "LatestRoute|Pool|session", "set": "AllSyncRoute|Pool|session" } } }
However, i noticed that when one of then memcache servers goes down, e.g., 10.1.5.100:11211, mcrouter will continue serving from the remaining server 10.1.5.101:11211, but will produce connection errors with attempts to connect to the memcache server that is down.
Is there a way to configure mcrouter so it can stop attempting connecting to the configured memcache server that has gone down?
The text was updated successfully, but these errors were encountered: