Re: 4.1.1-5914 Community Edition (build-5914) We’re running a rebalance and it appears to be causing lots of NodeUnavailable and OperationTimeout errors. The node ###.###.###.###:11210 that the key was mapped to is either down or unreachable. The SDK will continue to try to connect every 1000ms. …

Rebalance causing lots of NodeUnavailable and OperationTimeout Errors

PierreRoudaut March 24, 2020, 10:55am 2

Experiencing the exact same issue here. Do you know if the SDK automatically acknowledge adding and removal of new nodes ?

Topic		Replies	Views
NodeUnavailableException .NET SDK	2	1690	March 7, 2019
While adding new node, There comes TimeoutExceptions Couchbase Server	0	935	April 30, 2017
Time out and Key was mapped issues .NET SDK dot-net	1	2126	December 31, 2015
Unable to locate node errors in client during rebalance .NET SDK	3	4329	March 23, 2014
Rebalance Failure v4.0.0 Couchbase Server	1	2025	March 10, 2017