Closed GoogleCodeExporter closed 8 years ago
1.Timeout cloud not be avoid completely,it can be caused by such as
network,full gc that you can't control.But you can make your code to retry when
catch timeout exception.
2.I don't know why you need this info?
3.You can do this by logging,i don't want to supply this feature.
Thanks.
Original comment by killme2...@gmail.com
on 21 Nov 2012 at 10:08
1. Retrying is not a bad idea, with so many operations and just a few failing,
the performance hit of retrying should be imperceptible.
2. Having a timeout but not knowing which particular server produced it is a
problem if I aim to figure out the pattern and eventually a solution. It could
be an issue with GC but it could also be an issue with the Memcached server and
unless I know which one is giving me a hard time I can't diagnose the issue.
I think this small feature can be very easily implemented in
XMemcachedClient#latchWait method line 2561 with something like this:
private void latchWait(final Command cmd, final long timeout)
throws InterruptedException, TimeoutException {
if (!cmd.getLatch().await(timeout, TimeUnit.MILLISECONDS)) {
cmd.cancel();
throw new TimeoutException("Timed out(" + timeout
+ ") waiting for operation while connected to " +
connector.findSessionByKey(cmd.getKey()));
}
}
Original comment by claudio....@gmail.com
on 29 Nov 2012 at 12:28
Original comment by killme2...@gmail.com
on 11 Jan 2013 at 11:51
xmemcached 1.4.0 is released.
Original comment by killme2...@gmail.com
on 20 Feb 2013 at 9:03
Original issue reported on code.google.com by
claudio....@gmail.com
on 20 Nov 2012 at 10:12