Facing AmbiguousTimeoutException, SelectBucketFailedEvent, Unambiguous Timeout Exceptions

Java SDK
1

Hi Team,

I am getting Unambiguous and Ambiguous Timeout Exceptions after upgrading Java SDK to 3.0.6

Configuration are mentioned as below:-

Couchbase server :- Enterprise Edition 6.0.2 build 2413
Spring boot version :- 2.3.2
java-client- 3.0.6.jar
spring-boot-starter-data-couchbase-reactive-2.3.2.RELEASE.jar
spring-data-couchbase- 4.0.2.RELEASE .jar

image
image1290×263 70.3 KB

com.couchbase.client.core.error. AmbiguousTimeoutException : RemoveRequest, Reason: TIMEOUT\n\tat com.couchbase.client.core.msg.BaseRequest.cancel(BaseRequest.java:163)\n\tat com.couchbase.client.core.Timer.lambda$register$2(Timer.java:157)\n\tat com.couchbase.client.core.deps.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:672)\n\tat com.couchbase.client.core.deps.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:747)\n\tat com.couchbase.client.core.deps.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:472)\n\tat com.couchbase.client.core.deps.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.lang.Thread.run(Thread.java:748)\n

Kindly help for this issue.

2

I also get the same issue:

2021-01-22 21:11:27.884 ERROR 34172 — [nio-8080-exec-8] j.e.resource.webcontainer.jsf.context : com.couchbase.client.core.error.UnambiguousTimeoutException: GetRequest, Reason: TIMEOUT {“cancelled”:true,“completed”:true,“coreId”:“0xefdf98a100000001”,“idempotent”:true,“lastChannelId”:“EFDF98A100000001/000000005CAE04B7”,“lastDispatchedFrom”:“10.244.80.158:55737”,“lastDispatchedTo”:“172.28.174.142:11210”,“reason”:“TIMEOUT”,“requestId”:170,“requestType”:“GetRequest”,“retried”:0,“service”:{“bucket”:“buyer_hierarchy_dev”,“collection”:"_default",“documentId”:“id.gb”,“opaque”:“0xf5”,“scope”:"_default",“type”:“kv”},“timeoutMs”:2500,“timings”:{“totalMicros”:2512908}}
at com.couchbase.client.core.msg.BaseRequest.cancel(BaseRequest.java:163)
at com.couchbase.client.core.Timer.lambda$register$2(Timer.java:157)
at com.couchbase.client.core.deps.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:672)
at com.couchbase.client.core.deps.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:747)
at com.couchbase.client.core.deps.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:472)
at com.couchbase.client.core.deps.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:834)
Suppressed: java.lang.Exception: #block terminated with an error
at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:99)

3

@sushmit_K your operation timed out after it got sent onto the network. It could be the network or the server - your logs should also have orphan logging and over threshold logging which could indicate the latency of the response that came back. This does not look like to be an SDK issue.