.refresher.CarrierRefresher - Could not fetch config from bucket "price_datapool" against "192.168.103.134"

Java SDK
1

.
.
.
12:31:10.701 [cb-computations-1] DEBUG c.c.client.core.RequestHandler - Removing and disconnecting node slave3.hadoop.com/192.168.103.134.
12:31:10.701 [cb-computations-1] DEBUG c.c.client.core.RequestHandler - Got instructed to remove Node slave3.hadoop.com/192.168.103.134
12:31:10.701 [cb-computations-1] DEBUG com.couchbase.client.core.node.Node - [slave3.hadoop.com]: Got instructed to disconnect.
12:31:10.701 [cb-computations-1] DEBUG com.couchbase.client.core.node.Node - [slave3.hadoop.com]: Got instructed to disconnect.
12:31:10.701 [cb-computations-1] DEBUG com.couchbase.client.core.node.Node - [slave3.hadoop.com]: Instructing Service CONFIG to disconnect.
12:31:10.701 [cb-computations-1] DEBUG c.c.client.core.service.Service - [slave3.hadoop.com][ConfigService]: Got instructed to disconnect.
12:31:10.701 [cb-computations-1] DEBUG com.couchbase.client.core.node.Node - [slave3.hadoop.com]: Instructing Service VIEW to disconnect.
12:31:10.701 [cb-computations-1] DEBUG c.c.client.core.service.Service - [slave3.hadoop.com][ViewService]: Got instructed to disconnect.
12:31:10.701 [cb-computations-1] DEBUG c.c.client.core.service.Service - [slave3.hadoop.com][ViewService]: Initializing disconnect on Endpoint.
12:31:10.701 [cb-computations-1] DEBUG com.couchbase.client.core.node.Node - [slave3.hadoop.com]: Instructing Service BINARY to disconnect.
12:31:10.701 [cb-computations-1] DEBUG c.c.client.core.service.Service - [slave3.hadoop.com][KeyValueService]: Got instructed to disconnect.
12:31:10.701 [cb-computations-1] DEBUG c.c.client.core.service.Service - [slave3.hadoop.com][KeyValueService]: Initializing disconnect on Endpoint.
12:31:10.701 [cb-computations-1] INFO com.couchbase.client.core.node.Node - Disconnected from Node slave3.hadoop.com
12:31:10.701 [cb-computations-1] DEBUG com.couchbase.client.core.node.Node - Disconnected (CONNECTING) from Node slave3.hadoop.com/192.168.103.134
12:31:10.701 [cb-computations-1] DEBUG c.c.c.c.c.refresher.CarrierRefresher - Completed refreshing config for bucket “price_datapool”

A new cluster has been created.yes?
.
.
.
.
inserting ===>start
12:31:53.060 [cb-core-3-2] DEBUG c.c.c.c.c.refresher.CarrierRefresher - Could not fetch config from bucket “price_datapool” against “slave3.hadoop.com/192.168.103.134”.
com.couchbase.client.core.RequestCancelledException: Could not dispatch request, cancelling instead of retrying.
at com.couchbase.client.core.retry.RetryHelper.retryOrCancel(RetryHelper.java:51) [couchbase-core-io-1.1.3.jar:1.1.3]
at com.couchbase.client.core.RequestHandler.onEvent(RequestHandler.java:194) [couchbase-core-io-1.1.3.jar:1.1.3]
at com.couchbase.client.core.RequestHandler.onEvent(RequestHandler.java:73) [couchbase-core-io-1.1.3.jar:1.1.3]
at com.couchbase.client.deps.com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128) [couchbase-core-io-1.1.3.jar:1.1.3]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_21-ea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_21-ea]
at com.couchbase.client.deps.io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) [couchbase-core-io-1.1.3.jar:1.1.3]
at java.lang.Thread.run(Thread.java:619) [na:1.6.0_21-ea]
12:31:53.076 [cb-computations-3] DEBUG c.c.c.c.config.ConfigurationProvider - New Bucket price_datapool config proposed.
success: casId:1892859360173768 ; docID:Price_85646131
12:31:53.076 [cb-computations-3] DEBUG c.c.c.c.c.refresher.CarrierRefresher - Completed refreshing config for bucket "price_datapool"
touch:true
inserting end

2

how do you initialize connection to your cluster? what is it you are trying to do? what is your question?

First log extract shows that you probably failed over node slave3.hadoop.com? The SDK disconnected from this node.
Then it tries to refresh the cluster map before performing an operation, but it fails because it didn’t get a refreshed cluster map and the node it chose for update notifications is down.
After that, it does get notified of a new cluster map / cluster config (because of a failover/rebalance action?) at which point it seems to reconfigure itself correctly then perform the insertion and the touch.

3

If I donot do the reblance after auto failover, the sequential insert operation will slow down a lot,
so i want to know why.
AndI find that
the cluster of 3 nodes has been created ,that is , the node slave3.hadoop.com has been removed ,and if so, why does the exception ‘Could not fetch config from bucket “price_datapool” against “slave3.hadoop.com/192.168.103.134”’ occur ?