Frequent 'not_my_vbucket' errors hitting cluster via a load balancer

Hello,

The short answer is : do not use a load balancer.

From a resource management point of view:
You do not need to use a load balancer as Couchbase Cluster is managing all the nodes. Updating the configuration of all the nodes when you change them.

From an “applicaton”:
The way the sharding -distribution of the data- is done in Couchbase is not compliant with Load Balancer, simply because you have a single active copy of a data by cluster so the client calculate on which node the operation should be done (for example: get, set, add, remove, …).
So if you put a load balancer, the operation that the client sends may not go to the proper node and return you this exception.

Let me know if you need more information.

Tug
@tgrall