Rebalance causing lots of NodeUnavailable and OperationTimeout Errors

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. Until it can connect every operation routed to it will fail with this exception.

The operation has timed out.

Is this normal? Is there a way to mitigate this issue?

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

We still experience this issue. The only solution we’ve found is to stop and start all applications using Couchbase to get them to acknowledge the nodes removal.

1 Like