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'm using pylibmc but I think this is just a wrapper for functionality in libmemcached.
The situation is:
create a connection with num_replicas:1 on two servers (server_1, server_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)
stop server_2
check the main connection for the key. Connection error received.
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.
The text was updated successfully, but these errors were encountered:
Imported from Launchpad using lp2gh.
I'm using pylibmc but I think this is just a wrapper for functionality in libmemcached.
The situation is:
-- 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.
The text was updated successfully, but these errors were encountered: