@varun.velamuri thank you for your answer!
Here is additional information after research.
When the problem describes happens (indexes moving between Ready and Warm Up), there are 2 categories of errors in indexer.log.
The first one (repeating) is:
2020-05-13T10:41:00.514-07:00 [Warn] Indexer::validateIndexInstMap Bucket mybucket is not yet ready (err = MCResponse status=KEY_ENOENT, opcode=0x89, opaque=0, msg: ) Retrying(5)..
2020-05-13T10:41:00.713-07:00 [Error] StartDcpFeedOver(): MCResponse status=KEY_ENOENT, opcode=0x89, opaque=0, msg:
the second type of error (also repeating) is:
'd:\Couchbase\var\lib\couchbase\data\@2i\business_idx_ic_terminal_status_10511548744874879119_0.index\data.fdb.188', errno = 32: 'The process cannot access the file because it is being used by another process.'2020-05-13T10:47:05.722-07:00 [ERRO][FDB] Successfully used partially compacted file 'd:\Couchbase\var\lib\couchbase\data\@2i\business_idx_ic_terminal_status_10511548744874879119_0.index\data.fdb.189' for recovery replacing old file d:\Couchbase\var\lib\couchbase\data\@2i\business_idx_ic_terminal_status_10511548744874879119_0.index\data.fdb.188.
- System has 16 GB of RAM and sufficient disk space
- Data service 6 GB
- Index service 2 GB
- Full-text service 4 GB
- 2 GB for Windows
- No sign of performance degradation other than the error discussed here
- 5 buckets were configured
- buckets are usually not very large (typically < 10.000 documents), only 1 bucket has 700.000 documents * It has 1 large GSI secondary index of 700 MB and many others of 20 MB each
- GSI indexing is set to “circular write”, compaction set every day 00:00 (default)
We are now currently looking into dropping the large secondary index, but not sure whether this could be the problem.
We are also considering increasing the memory for Indexer service, but we could not find any sizing recommendations for Index service (only for data service is well explained here: https://docs.couchbase.com/server/current/install/sizing-general.html)
Do you have any recommendation? And what could be causing the error reported, from your experience?