Hi Nolan,
From: Nolan Dubeau <[email protected]>
Date: Friday, May 9, 2014 at 8:47 AM
Subject: net.spy.memcached.OperationTimeoutException
>Hello,
>
>I've been using the Couchbase Java SDK and am frequently encountering
>errors such as this:
>
>Error Type: net.spy.memcached.OperationTimeoutException
> : [N/A]
>Error Messages: Timeout waiting for value: waited 2,500 ms.
> Node status: Connection Status { 10.xx.xx.xx/10.xx.xx.xx:11210 active:
>false, authed: true, last read: 391,748 ms ago }
>
>
>My application code is connecting using the external URL of the CB
>server, however the error is reporting the internal IP of the CB node.
>
>There does not seem tos be any pattern as to why/when these errors occur.
>
>Does anyone have any insight as to how to resolve?
>
>
>
First note is that your error message seems to indicate you¹re using an
old version of the SDK. That ³last read² is correct in later versions.
Second, there can be a large number of reasons for timeouts. JVM GC is
one possible cause. Something happening at the cluster side (like lots of
background fetches) is another possible cause. Unfortunately, we can¹t
exactly tell from this error message.
I would recommend a few things:
1. See if it correlates to JVM GC or JIT activity. This isn¹t likely, but
good to rule out.
2. Check the timings internal to the client to see if it¹s regularly
high[a].
3. Check the timings at the cluster to see if they correlate[b].
The combination of 2 and 3 will let you know where to dig deeper.
Thanks,
Matt
a: See ³enhanced profiling²:
http://blog.couchbase.com/whats-new-couchbase-java-sdk-12
b: See docs on ³cbstats timings²:
http://docs.couchbase.com/couchbase-manual-2.5/cb-cli/#getting-server-timin
gs
--
Matt Ingenthron
Couchbase, Inc.
--
You received this message because you are subscribed to the Google Groups
"Couchbase" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
