killme2008 / killme2008/xmemcached
Memcached TimeOut Exception
- Dominant language
- Java
- Stars
- 764
- Forks
- 271
- PR merge metrics
- No merged PRs in 30d
Description
Getting following exception while set,add,delete and get , I am using xmemcached-1.3.8.jar. Please let me know below issue is fixed in latest version of xmemcached?
java.util.concurrent.TimeoutException: Timed out(200) waiting for operation
at net.rubyeye.xmemcached.XMemcachedClient.latchWait(XMemcachedClient.java:2565)
at net.rubyeye.xmemcached.XMemcachedClient.sendStoreCommand(XMemcachedClient.java:2548)
at net.rubyeye.xmemcached.XMemcachedClient.set(XMemcachedClient.java:1312)
at net.rubyeye.xmemcached.XMemcachedClient.set(XMemcachedClient.java:1370)
at net.rubyeye.xmemcached.XMemcachedClient.set(XMemcachedClient.java:1357)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the stack trace in XMemcachedClient.java, especially latchWait, sendStoreCommand, and the set entry points. Determine why set, add, delete, and get reach the 200 ms timeout when using xmemcached-1.3.8, then verify whether the behavior is fixed in a later version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, memcached
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100