> On Mar 9, 2015, at 8:30 AM, Michael Mayer <[email protected]> wrote: > > 10:23:45.785649 HTTP+: #155: --> 201 (144.1 ms)2015/03/09 10:23:49 > go-couchbase: call to Do("groupdata::08::2015::03::09") in > github.com/couchbaselabs/go-couchbase > <http://github.com/couchbaselabs/go-couchbase>.(*Bucket).casNext took > 18.9097081s > 10:23:49.848933 WARNING: Couldn't interpret error type *net.OpError, value > WSARecv tcp 10.10.3.39:61617: A connection attempt failed because the > connected party did not properly respond after a period of time, or > established connection failed because connected host has failed to respond. > -- base.ErrorAsHTTPStatus() at error.go:63
The Sync Gateway is having serious problems communicating with Couchbase Server — the errors above are from the SDK that the Gateway uses to talk to the database. The first shows an extremely long time to service a request (19 sec!), and the second looks like a timeout establishing a TCP connection. I think something’s seriously wrong with either the network connectivity from SG to the database cluster, or with the cluster itself. —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/DB00F54D-27D8-4CE3-939B-DFAE94A4E395%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
