We are using Community Edition 5.0.1 build 5003 in a single node deployment running on Windows. This node is running on Windows 10 laptop (for development purposes), but we notice that occasionally the Indexer.exe process will appears to hang. The symptoms we’re seeing are constant ~25% CPU even when there’s no external activity in the database and indexes report 100% complete.
The bigger issue is that when Couchbase gets in this state the indexes fail to update i.e. we insert new data into a bucket and they are not visible via N1QL SELECT queries although we can see the data in bucket. We tried compacting the index, no help. We tried running a N1QL query from the console using ‘request_plus’ scan consistency and the query times out.
The only index we have on the bucket is a simple secondary index with a single, non-unique string (user id) field as the index. The bucket itself has < 1000 items in it.
The only ‘fix’ thus far is to restart the Couchbase service which is not desirable.
Any ideas on the source of this type of issue?
Thanks in advance!