How does Couchbase Server distribute the load over replicated indexes

Enterprise 6.5

We’re trying to reason about scaling out our index nodes.

How are query’s distributed over replicated indexes?

I know for instance, that the sdk will round robin requests to the set of available query nodes, and thus we can reason about how adding or subtracting one would help us?

How does it work for the index nodes.

Please help?

Checkout Item 9

During start of the index scan based on the load of the indexer services it chose one of the equivalent or replicated indexes.

1 Like