Judging from the logs, the problem seems to be establishing the actual TCP connection. In other words, for this particular error this may not be so much an issue of resources as it is an issue of accessibility.
I forget if there’s a reference manual or something for AWS, but you should make sure that the hostnames you give to your cluster (i.e. the nodes in the cluster) should also be reachable from within the client. I’m guessing that ‘1.2.3.4’ is really a redacted version of the actual IP the client is trying to reach. Can you make sure you can ping that address? Can you verify the given port is open? > On Jan 15, 2015, at 10:36 AM, Dump Hole <[email protected]> wrote: > > Hi Mark! > > Thank you for helping me. Got more results back after enabling the > LCB_LOGLEVEL=5 > > 12931ms [I0] {9907} [DEBUG] (lcbio_mgr - L:416) <1.2.3.4:8092> (HE=0x39efd90) > Creating new connection because none are available in the pool > 12931ms [I0] {9907} [DEBUG] (lcbio_mgr - L:321) <1.2.3.4:8092> (HE=0x39efd90) > Starting connection on I=0x39ef520 > 12931ms [I0] {9907} [INFO] (connection - L:441) <1.2.3.4:8092> > (SOCK=0x39f02b0) Starting. Timeout=75000000us > 12931ms [I0] {9907} [TRACE] (connection - L:258) <1.2.3.4:8092> > (SOCK=0x39f02b0) Got event handler for new connection > 12931ms [I0] {9907} [TRACE] (connection - L:305) <1.2.3.4:8092> > (SOCK=0x39f02b0) Scheduling asynchronous watch for socket. > 12961ms [I0] {9907} [TRACE] (connection - L:258) <1.2.3.4:8092> > (SOCK=0x39f02b0) Got event handler for new connec > tion > 12961ms [I0] {9907} [INFO] (connection - L:116) <1.2.3.4:8092> > (SOCK=0x39f02b0) Connected > 12961ms [I0] {9907} [DEBUG] (lcbio_mgr - L:271) <1.2.3.4:8092> (HE=0x39efd90) > Received result for I=0x39ef520,C=0 > x39f02b0; E=0x0 > 12961ms [I0] {9907} [DEBUG] (lcbio_mgr - L:223) <1.2.3.4:8092> (HE=0x39efd90) > Assigning R=0x39efb20 SOCKET=0x39f0 > 2b0 > 12961ms [I0] {9907} [DEBUG] (ioctx - L:101) <1.2.3.4:8092> > (CTX=0x39f0c80,unknown) Pairing with SOCK=0x39f02b0 > 12997ms [I0] {9907} [DEBUG] (ioctx - L:151) <1.2.3.4:8092> > (CTX=0x39f0c80,mgmt/capi) Destroying. PND=0,ENT=1,SORC > =1 > 12997ms [I0] {9907} [INFO] (lcbio_mgr - L:491) <1.2.3.4:8092> (HE=0x39efd90) > Placing socket back into the pool. I > =0x39ef520,C=0x39f02b0 > 12997ms [I0] {9907} [DEBUG] (lcbio_mgr - L:416) <1.2.3.4:11210> > (HE=0x39f2bb0) Creating new connection because no > ne are available in the pool > 12997ms [I0] {9907} [DEBUG] (lcbio_mgr - L:321) <1.2.3.4:11210> > (HE=0x39f2bb0) Starting connection on I=0x39ef4c0 > 12997ms [I0] {9907} [INFO] (connection - L:441) <1.2.3.4:11210> > (SOCK=0x2fc13d0) Starting. Timeout=2500000us > 12997ms [I0] {9907} [TRACE] (connection - L:258) <1.2.3.4:11210> > (SOCK=0x2fc13d0) Got event handler for new conne > ction > 12997ms [I0] {9907} [TRACE] (connection - L:305) <1.2.3.4:11210> > (SOCK=0x2fc13d0) Scheduling asynchronous watch f > or socket. > 15500ms [I0] {9907} [ERROR] (server - L:476) <NOHOST:NOPORT> > (SRV=0x392ab00,IX=0) Got error for connection! (OS=0) > 15500ms [I0] {9907} [WARN] (server - L:374) <NOHOST:NOPORT> > (SRV=0x392ab00,IX=0) Failing command (pkt=0x39f1590, opaqu > e=0, opcode=0x0) with error 0x17 > 15500ms [I0] {9907} [TRACE] (confmon - L:292) Start refresh requested > 15500ms [I0] {9907} [ERROR] (connection - L:118) <1.2.3.4:11210> > (SOCK=0x2fc13d0) Failed: lcb_err=0x17, os_errno= > 0 > 15500ms [I0] {9907} [DEBUG] (lcbio_mgr - L:271) <1.2.3.4:11210> > (HE=0x39f2bb0) Received result for I=0x39ef4c0,C= > (nil); E=0x17 > Couchbase::Error::Timeout - failed to get value, Client-Side timeout exceeded > for operation. Inspect network condition > s or increase the timeout (key="printer_1", error=0x17) > > > I just upgraded the instance to something slightly more beefy, but still got > the error. This time it's a brand new CB instance, not crowded with any > documents. > > > On Thursday, January 15, 2015 at 9:37:18 AM UTC-8, M. Nunberg wrote: > It would indeed seem you are having issues with the AWS instance. In this > case you seem to be timing out when performing a key-value operation (it > seems you’re doing a get) which is an entirely different issue than what you > were seeing before. > > Adding logging would certainly help disambiguate most issues, in addition to > LCB_OPTIONS, set LCB_LOGLEVEL=5 in your environment (it will log to stderr). > >> On Jan 15, 2015, at 9:33 AM, Dump Hole <[email protected] <javascript:>> >> wrote: >> >> FYI, it didn't take long to timeout. It displayed that message within 2-3 >> seconds. I would assume timeout is set to 75 secs as specified by the >> connection_timeout parameter. >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > 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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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.
