TimeoutException when trying to connect to a remote cluster

1,014 views
Skip to first unread message

Sebastien ARBOGAST

unread,
Feb 11, 2015, 8:56:31 AM2/11/15
to couc...@googlegroups.com
I set up a Couchbase + Sync Gateway cluster as described in Traun Leyden's post there: http://tleyden.github.io/blog/2014/12/15/running-a-sync-gateway-cluster-under-coreos-on-aws/

The cluster seems to be running fine, I can access the web console for all my machines.
I also opened ports 8092 and 11209-11211 to all IP addresses. Now I'm trying to connect to this cluster using the Java SDK (2.1).

cluster = CouchbaseCluster.create(config.nodes)
bucket = cluster.openBucket(config.bucket, config.password)

But the second call gives me a TimeoutException:

[main] INFO com.couchbase.client.core.CouchbaseCore - CoreEnvironment: {sslEnabled=false, sslKeystoreFile='null', sslKeystorePassword='null', queryEnabled=false, queryPort=8093, bootstrapHttpEnabled=true, bootstrapCarrierEnabled=true, bootstrapHttpDirectPort=8091, bootstrapHttpSslPort=18091, bootstrapCarrierDirectPort=11210, bootstrapCarrierSslPort=11207, ioPoolSize=8, computationPoolSize=8, responseBufferSize=16384, requestBufferSize=16384, kvServiceEndpoints=1, viewServiceEndpoints=1, queryServiceEndpoints=1, ioPool=NioEventLoopGroup, coreScheduler=CoreScheduler, eventBus=DefaultEventBus, packageNameAndVersion=couchbase-java-client/2.1.0 (git: 2.1.0), dcpEnabled=false, retryStrategy=BestEffort, maxRequestLifetime=75000, retryDelay=com.couchbase.client.core.time.ExponentialDelay@574b560f, reconnectDelay=com.couchbase.client.core.time.ExponentialDelay@ba54932, observeIntervalDelay=com.couchbase.client.core.time.ExponentialDelay@28975c28, keepAliveInterval=30000}
[cb-io-1-3] INFO com.couchbase.client.core.node.Node - Connected to Node ec2-node1.compute-1.amazonaws.com
[cb-io-1-1] INFO com.couchbase.client.core.node.Node - Connected to Node ec2-node2.compute-1.amazonaws.com
[cb-io-1-2] INFO com.couchbase.client.core.node.Node - Connected to Node ec2-node3.compute-1.amazonaws.com
Exception in thread "main" java.lang.RuntimeException: java.util.concurrent.TimeoutException
at com.couchbase.client.java.util.Blocking.blockForSingle(Blocking.java:93)
at com.couchbase.client.java.CouchbaseCluster.openBucket(CouchbaseCluster.java:108)
at com.couchbase.client.java.CouchbaseCluster.openBucket(CouchbaseCluster.java:99)
at com.couchbase.client.java.CouchbaseCluster.openBucket(CouchbaseCluster.java:89)
at com.couchbase.client.java.Cluster$openBucket.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128)
at CouchbaseService.<init>(CouchbaseService.groovy:14)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77)
at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:102)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:57)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:230)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:242)
at WebServer.main(WebServer.groovy:12)
Caused by: java.util.concurrent.TimeoutException
... 19 more

How can I check whether my Couchbase server cluster is correctly configured to allow remote access? Any idea what I forgot?

Shital

unread,
Jul 29, 2015, 2:58:27 AM7/29/15
to Couchbase, sebastien...@gmail.com
Hi
Have you got any solution for the below issue, we are facing same one.

Thanks
Reply all
Reply to author
Forward
0 new messages