Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check status of memcache #265

Open
chilumbugeorge opened this issue Aug 1, 2018 · 0 comments
Open

Check status of memcache #265

chilumbugeorge opened this issue Aug 1, 2018 · 0 comments

Comments

@chilumbugeorge
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant