Details
-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
2.0.0
-
None
-
Security Level: Public
-
Node: v0.10.29
Couchbase: v2.5.1
Description
Running multiple .replace ops (also have this in .counter) parallel (20+), seem to run into timeout issues randomly.
"Client-Side timeout exceeded for operation. Inspect network conditions or increase the timeout"
We run 6 buckets and the most active bucket seem to run into this issue a lot. The couchbase servers metrics do not show anything ordinary and logs act like normal too. Server itself isn't busy at all, idle.
Ran into this on development (single) and AWS-test setup (multiple). It just isn't as stable as the v1 was, we never had these kind of issues processing this small amount of data. I just cannot count on it running production with this.
There is little to no latency between the nodes and the couchbases;
64 bytes from 172.31.33.*: icmp_seq=1 ttl=64 time=0.199 ms
64 bytes from 172.31.0.*: icmp_seq=1 ttl=64 time=0.566 ms