Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
We are seeing bursts of this exception in production for various memcache operations. Stack traces look similar to this:
We could not 100% pin point what is causing it but one of the suspects is how XMemcached handles server responses.
One situation that can be reproduced in a standalone java project is how XMemcached client handles server responses for values greater than 1M (> default max size in memcache).
In the code below our expectation is to get MemcachedServerException with message "object too large for cache" for "set" operation but instead we are getting java.util.concurrent.TimeoutException
It is worth noting that spymemcached client used in the same code does handle server response properly and returns "SERVER_ERROR object too large for cache"
Hi, i am sorry so late to look into this issue.
But i can't reproduce by above code
In 2.1.0, i tweaked the performance of binary protocol implementation.The binary protocol in old xmemcached versions are not good enough, it's performance is less than text protocol command factory.But in 2.1.0, it catches up.
You may wan to try it when you are free.And if you have more info for this issue ,please let me known, thanks.
Hi - Do you have an estimated date for this release please? It is one that has been plaguing us for over a year now and we have a really critical release in November for which we desperately need this fix. Is there any way we can persuade you to release this immediately?
I can release a minor version today.
2016-10-27 2:14 GMT+08:00 sudhakv email@example.com: