Indeed oslo.cache could be a track to follow in this context.
As discussed on IRC with Mark he will start by removing the oslo.cache changes (before 2.1.0) which move from memcached to pymemcache.
Also it could be worth to grep oslo.cache/pymemcache/memcache errors to seen where is exactly the issue here.
I used the serde module [1] to keep serialization/deserialization compatible with the data previously stored [2], maybe something went wrong on this side and your data are not compatible for some reasons, it could be a clue.
Indeed oslo.cache could be a track to follow in this context.
As discussed on IRC with Mark he will start by removing the oslo.cache changes (before 2.1.0) which move from memcached to pymemcache.
Also it could be worth to grep oslo.cache/ pymemcache/ memcache errors to seen where is exactly the issue here.
I used the serde module [1] to keep serialization/ deserialization compatible with the data previously stored [2], maybe something went wrong on this side and your data are not compatible for some reasons, it could be a clue.
[1] https:/ /github. com/openstack/ oslo.cache/ blob/8a8248d764 bbb1db6c0089a58 745803c03e38fdb /oslo_cache/ _memcache_ pool.py# L41,L42 /pymemcache. readthedocs. io/en/latest/ apidoc/ pymemcache. serde.html# module- pymemcache. serde
[2] https:/