Restore, indexes and "mutations remaining" statistics

[amit.kulkarni]

Hi @LeonidGvirtz,

Can you please upload indexer.log files from all the nodes? After looking at the logs, I can better explain the root cause of the problems, if any.

From the other topics you have created

Partitioned index distribution across cluster nodes

Hi I have a 3-node cluster running Couchbase Server 5.5.2. Index service runs on all three nodes. On this cluster, I have a bucket with UUIDs served as document ids. I create a number of partitioned indexes like this: CREATE INDEX idx_attr1 ON bucket1(lower(attr1)) PARTITION BY HASH(META().Id); I see that the load on nodes is distributed very much unequally, even though, partitioning by a uniformly distributed attribute (UUID) is expected to distribute the index more or less uniformly. One of…

Partitioned index doesn't get distributed over all available nodes

Hi When I create partitioned indexes on a 3-node cluster (version 5.5.2), indexes sometimes don’t get distributed over all available nodes. Since all 3 nodes run indexer service, I assume that Couchbase is supposed to distribute the index on all available nodes. In fact, I see most of my indexes distributed on 2 nodes only. The issue is not related to a specific node. To find a workaround, I decided to specify the list of the nodes for an index explicitly, even though I understand that the lis…

what I can see is, partition distribution (3, 3, 2) looks fine to me (as mentioned by @prathibha). With partition distribution (3, 3, 2), the ratio 12M:12M:8M seems like a uniform distribution among the partitions.