Couchbase Indexer in warmup state

Couchbase Server
1

We are using Couchbase Community Edition 7.0.2 build 6703 and the Index service has been in warmup status for a long time.
Upon reviewing the indexer logs, we are seeing the following logs.

2023-12-08T01:16:33.701+00:00 [INFO][FDB] Forestdb opened database file /datadrive/couchbase/data/@2i/CustomUserViews_adv_CustomUserViews_01_13430350185075968771_0.index/data.fdb.3
2023-12-08T01:16:33.703+00:00 [Info] NewForestDBSlice(): file version ForestDB v2.x format
2023-12-08T01:16:33.704+00:00 [Info] ForestDBSlice:NewForestDBSlice Created New Slice Id 0 IndexInstId 13430350185075968771 WriterThreads 1
2023-12-08T01:16:33.704+00:00 [Info] Indexer::initPartnInstance Initialized Slice:
Index: 13430350185075968771 Slice: SliceId: 0 File: /datadrive/couchbase/data/@2i/CustomUserViews_adv_CustomUserViews_01_13430350185075968771_0.index Index: 13430350185075968771
2023-12-08T01:16:33.705+00:00 [Info] StorageMgr::updateIndexSnapMapForIndex IndexInst 13430350185075968771 Partitions [0]
2023-12-08T01:16:33.715+00:00 [Info] StorageMgr::openSnapshot IndexInst:13430350185075968771 Partition:0 Attempting to open snapshot (SnapshotInfo: seqnos: 926, 926, 18 committed:true)
2023-12-08T01:16:33.715+00:00 [Info] ForestDBSlice::OpenSnapshot SliceId 0 IndexInstId 13430350185075968771 Creating New Snapshot SnapshotInfo: seqnos: 926, 926, 18 committed:true
2023-12-08T01:16:33.715+00:00 [Error] ForestDBSnapshot::Open
Unexpected Error Opening Main DB Snapshot (/datadrive/couchbase/data/@2i/CustomUserViews_adv_CustomUserViews_01_13430350185075968771_0.index) SeqNum 926 FDB_RESULT_NO_DB_INSTANCE
panic: Unable to open snapshot -FDB_RESULT_NO_DB_INSTANCE

Any pointers for the above log snippets?

We are seeing the above entries repeating quite often.

We restarted the Coucnbase Server but with no luck.

Any idea what panic: Unable to open snapshot -FDB_RESULT_NO_DB_INSTANCE means?.

Thanks

2

I’m looking in here Loading...
You should be able to see the public issues after creating an account.

From what I find - the solution is to delete all the forestdb index files which are in a data/2@i directory.

3

Temp solution for this issue. You can restart each index nodes indexer process. Most probably problematic nodes indexer pods will not start properly and your indexes might not turn as ready due to some internal issues in side node. If you tailf indexer.log file you will understand that what might be the problem.

Restart that pod or node to solve this problem.

Even have raised case with vendor. Still developing team is investigating on this new bug.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.