Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.7.4
-
None
-
None
-
1
Description
Steps to reproduce:
1. Create a cluster with 1 index/query node and 2 data service nodes
2. Mention index/query node IP address alone as part of the SDK bootstrap connection which will force the bootstrap connection to happen using HTTP
2019/05/08 22:18:40.669|WARN| Could not bootstrap with CCCP. (Authentication failed for user 'travel-sample') (Authentication failed for user 'travel-sample') (Authentication failed for user 'travel-sample') (Authentication failed for user 'travel-sample')|Couchbase.Core.ClusterController|
|
2019/05/08 22:18:40.720|INFO|Bootstrapping from http://10.111.191.101:8091/pools |Couchbase.Configuration.Server.Providers.Streaming.HttpServerConfig|
|
2019/05/08 22:18:40.953|INFO|Bootstrapped from http://10.111.191.101:8091/pools |Couchbase.Configuration.Server.Providers.Streaming.HttpServerConfig|
|
2019/05/08 22:18:41.032|INFO|o3-Creating the Servers list using rev#24821 |Couchbase.Configuration.ConfigContextBase|
|
3. While client SDK client is performing mutations, perform a swap rebalance for one of the data nodes in the cluster
4. As part of the Rebalance operation client SDK will receive the new cluster config, but the new cluster config will be ignored by the SDK client and will make use of the previous cluster config and cause timeout errors.
2019/05/08 22:20:11.717|DEBUG|Queueing config rev#25106 for [travel-sample]. |Couchbase.Core.ClusterController|
|
2019/05/08 22:20:11.717|DEBUG|Processing config rev#25106 |Couchbase.Core.ClusterController|
|
2019/05/08 22:20:11.724|WARN|No ConfigObserver found for bucket [travel-sample] |Couchbase.Configuration.Server.Providers.ConfigProviderBase|
|