Hi,
I have been trying to debug issues we are having with spymemcached (2.8.12) involving timeouts. We have 9 tomcat instances using 7 memcached instances and seeming randomly get timeout exceptions. Our peak usage is around 300 operations/second, but are seeing exceptions well below that level of usage
I have spent the day trying out different configuration options, even extending the timeout to 1 second, but am still seeing regular timeouts. The memcached server seems to be doing almost nothing, so I'm guessing that the problem is inside of spymemcached. I know that there have been some conversations about this issue in this group, but couldn't tell which ones are still current and if there are configuration options that are recommended for high throughput.
thanks!
Michael
Here are selected bits of the stack trace:
net.spy.memcached.OperationTimeoutException: Timeout waiting for value
at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1036)
at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1051)
...
Caused by: net.spy.memcached.internal.CheckedOperationTimeoutException: Timed out waiting for operation - failing node: /...
at net.spy.memcached.internal.OperationFuture.get(OperationFuture.java:160)
at net.spy.memcached.internal.GetFuture.get(GetFuture.java:62)
at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1026)