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
If a php request OOM's while requesting a key from memcached, then the next request (using persistent connections) will be given the value for that last request regardless of what key it actually requested. This obviously results in very unfun behavior application-side 😬
This is likely the same thing that was reported here: https://bugs.php.net/bug.php?id=74235. I wanted to open up a Github issue to help others that are looking for an explanation to some pretty maddening behavior :)
If a php request OOM's while requesting a key from memcached, then the next request (using persistent connections) will be given the value for that last request regardless of what key it actually requested. This obviously results in very unfun behavior application-side 😬
I've created a repo for easy replication: https://github.com/WPprodigy/memcache-inconsistency-debugging, using the latest release of this extension.
The text was updated successfully, but these errors were encountered: