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

num_replicas works when server goes down but not when it comes back up #64

Closed
m6w6 opened this issue Jan 20, 2020 · 1 comment
Closed

Comments

@m6w6
Copy link
Collaborator

m6w6 commented Jan 20, 2020

Imported from Launchpad using lp2gh.


I'm using pylibmc but I think this is just a wrapper for functionality in libmemcached.

The situation is:

  1. create a connection with num_replicas:1 on two servers (server_1, server_2)
  2. add a key to this connection (note the this connection does show this new value, server_1 directly does not, server_2 directly does)
  3. stop server_2
  4. check the main connection for the key. Connection error received.
  5. check the main connection again for the key, key is found so replicas did work (checking server_1 directly also shows the key)

-- all good so far --

Now, bring back up server_2.
check the main connection for the key. Not found!
check server_2 directly for the key, not found.
check server_1 directly for the key, found!

It seems to me that in this situation, the main connection should find the key still, regardless of server_2 coming back up. I am imagining situations where people have an autostart in case the service goes down.

@m6w6
Copy link
Collaborator Author

m6w6 commented Jan 27, 2020

See also #21

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

No branches or pull requests

1 participant