java.lang.RuntimeException: com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: connection timed out: /10.93.44.37:8091

Couchbase JIRA | Jeff Dillon | 4 months ago
  1. 0

    +Problem+ clusterManager.Info() consistently returns a timeout exception when one of the cluster nodes is down but not yet failed over. +Request+ The method should return the information on the healthy nodes if at least one of the healthy nodes is in the client bootstrap list. Some Key/Value requests (to other nodes) by comparison still succeed when the cluster is in this state +Steps to Reproduce+ * Create a test directory and make it the current working directory * Get the latest Couchbase Java SDK: wget http://packages.couchbase.com/clients/java/2.3.0/Couchbase-Java-Client-2.3.0.zip * Unzip the file * Change directory to ./Couchbase-Java-Client-2.3.0 * Copy the attached App.java to this location * Edit App.java to include the required IP addresses for the Couchbase cluster * Compile and run with the following: javac -cp couchbase-java-client-2.3.0.jar:rxjava-1.1.5.jar:couchbase-core-io-1.3.0.jar: App.java java -cp .:couchbase-java-client-2.3.0.jar:rxjava-1.1.5.jar:couchbase-core-io-1.3.0.jar: App Note the timeout exception if one of the nodes is down (and not yet failed over). The expectation is that the call would return info on the available nodes if one of the bootstrap nodes is available. Error: Exception in thread "main" java.lang.RuntimeException: com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: connection timed out: /10.93.44.37:8091 at com.couchbase.client.java.util.Blocking.blockForSingle(Blocking.java:82) at com.couchbase.client.java.cluster.DefaultClusterManager.info(DefaultClusterManager.java:56) at com.couchbase.client.java.cluster.DefaultClusterManager.info(DefaultClusterManager.java:51) at x.y.ConnectionTester.main(ConnectionTester.java:15) Caused by: com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: connection timed out: /10.93.44.37:8091 at com.couchbase.client.deps.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:220) at com.couchbase.client.deps.io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38) at com.couchbase.client.deps.io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:120) at com.couchbase.client.deps.io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358) at com.couchbase.client.deps.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:374) at com.couchbase.client.deps.io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112) at com.couchbase.client.deps.io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) at java.lang.Thread.run(Thread.java:745)

    Couchbase JIRA | 4 months ago | Jeff Dillon
    java.lang.RuntimeException: com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: connection timed out: /10.93.44.37:8091
  2. 0

    +Problem+ clusterManager.Info() consistently returns a timeout exception when one of the cluster nodes is down but not yet failed over. +Request+ The method should return the information on the healthy nodes if at least one of the healthy nodes is in the client bootstrap list. Some Key/Value requests (to other nodes) by comparison still succeed when the cluster is in this state +Steps to Reproduce+ * Create a test directory and make it the current working directory * Get the latest Couchbase Java SDK: wget http://packages.couchbase.com/clients/java/2.3.0/Couchbase-Java-Client-2.3.0.zip * Unzip the file * Change directory to ./Couchbase-Java-Client-2.3.0 * Copy the attached App.java to this location * Edit App.java to include the required IP addresses for the Couchbase cluster * Compile and run with the following: javac -cp couchbase-java-client-2.3.0.jar:rxjava-1.1.5.jar:couchbase-core-io-1.3.0.jar: App.java java -cp .:couchbase-java-client-2.3.0.jar:rxjava-1.1.5.jar:couchbase-core-io-1.3.0.jar: App Note the timeout exception if one of the nodes is down (and not yet failed over). The expectation is that the call would return info on the available nodes if one of the bootstrap nodes is available. Error: Exception in thread "main" java.lang.RuntimeException: com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: connection timed out: /10.93.44.37:8091 at com.couchbase.client.java.util.Blocking.blockForSingle(Blocking.java:82) at com.couchbase.client.java.cluster.DefaultClusterManager.info(DefaultClusterManager.java:56) at com.couchbase.client.java.cluster.DefaultClusterManager.info(DefaultClusterManager.java:51) at x.y.ConnectionTester.main(ConnectionTester.java:15) Caused by: com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: connection timed out: /10.93.44.37:8091 at com.couchbase.client.deps.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:220) at com.couchbase.client.deps.io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38) at com.couchbase.client.deps.io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:120) at com.couchbase.client.deps.io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358) at com.couchbase.client.deps.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:374) at com.couchbase.client.deps.io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112) at com.couchbase.client.deps.io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) at java.lang.Thread.run(Thread.java:745)

    Couchbase JIRA | 4 months ago | Jeff Dillon
    java.lang.RuntimeException: com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: connection timed out: /10.93.44.37:8091
  3. 0

    +Problem+ bucketManager.Info() consistently returns a timeout exception when one of the cluster nodes is down but not yet failed over. +Request+ The method should return the information on the bucket if at least one of the healthy nodes is in the client bootstrap list. +Steps to Reproduce+ Create a test directory and make it the current working directory Get the latest Couchbase Java SDK: wget http://packages.couchbase.com/clients/java/2.3.2/Couchbase-Java-Client-2.3.2.zip Unzip the file Change directory to ./Couchbase-Java-Client-2.3.2 Copy the attached App.java to this location Edit App.java to include the required IP addresses for the Couchbase cluster Compile and run with the following: javac -cp couchbase-java-client-2.3.2.jar:rxjava-1.1.8.jar:couchbase-core-io-1.3.2.jar: App.java java -cp .:couchbase-java-client-2.3.2.jar:rxjava-1.1.8.jar:couchbase-core-io-1.3.2.jar: App Note the timeout exception if one of the nodes is down (and not yet failed over). The expectation is that the call would return info on bucket if one of the bootstrap nodes is available. Exception in thread "main" java.lang.RuntimeException: com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: connection timed out: /10.111.150.102:8091 at com.couchbase.client.java.util.Blocking.blockForSingle(Blocking.java:82) at com.couchbase.client.java.bucket.DefaultBucketManager.info(DefaultBucketManager.java:122) at App.main(App.java:45) Caused by: com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: connection timed out: /10.111.150.102:8091 at com.couchbase.client.deps.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:216) at com.couchbase.client.deps.io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38) at com.couchbase.client.deps.io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:120) at com.couchbase.client.deps.io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:408) at com.couchbase.client.deps.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:402) at com.couchbase.client.deps.io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:140) at com.couchbase.client.deps.io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) at java.lang.Thread.run(Thread.java:745)

    Couchbase JIRA | 3 months ago | Jeff Dillon
    java.lang.RuntimeException: com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: connection timed out: /10.111.150.102:8091
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException

      connection timed out: /10.93.44.37:8091

      at com.couchbase.client.deps.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run()
    2. com.couchbase.client
      DefaultThreadFactory$DefaultRunnableDecorator.run
      1. com.couchbase.client.deps.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:220)
      2. com.couchbase.client.deps.io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38)
      3. com.couchbase.client.deps.io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:120)
      4. com.couchbase.client.deps.io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
      5. com.couchbase.client.deps.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:374)
      6. com.couchbase.client.deps.io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
      7. com.couchbase.client.deps.io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
      7 frames
    3. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:745)
      1 frame