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

potential memcached client incompatibility #817

Closed
nerdvegas opened this issue Dec 5, 2019 · 0 comments · Fixed by #818
Closed

potential memcached client incompatibility #817

nerdvegas opened this issue Dec 5, 2019 · 0 comments · Fixed by #818
Labels

Comments

@nerdvegas
Copy link
Contributor

We have seen a potential memcached serialization issue recently, which may be an incompatibility introduced between memcached v1.53 and v1.59.

This is not the same issue, but shows that incompatibilities like this are possible: linsomniac/python-memcached#140

Symptom: On some occasions, package.py data has timestamp field as long rather than int, causing package serialization to fail. The problem goes away if memcached is disabled.

Suggestion: Add the memcached client version number to the keys used to write/read memcache, so that there is no overlap between different memcached clients (and by extension newer/older rez versions). This is easy to do and does not come at any cost.

I don't want to spend a lot of time digging into this issue, since a port to redis is on the cards anyway. I think there's a reasonable chance the fix suggested above will work.

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

Successfully merging a pull request may close this issue.

1 participant