The following warning is seen in the logs: ‘Could not find nbtr iterator… skipping !!’?
Jan 15 2020 07:05:01 GMT: WARNING (query): (ai_btree.c:568) Could not find nbtr iterator.. skipping !!
This is not expected in a healthy cluster and would need attention if warning is constantly occurring.
The warning indicates that there is a secondary index key with no corresponding digests (a bin value for which there are no records). It could be because a primary index (and corresponding record) got deleted, but the secondary index still exists even though garbage collection worked as expected in the previous run.
Or this would occur when a running query had issues traversing the secondary index tree for that particular query and could not find an iterator for that particular section of the secondary index tree.
The impact could be minimal or none at all if there was no relevant data from that part of the tree. It could potentially mean that partial results were returned during that query.
If warning occured only once, it could mean that this is a benign issue and the subsequent round of garbage collection corrected the tree structure.
SINDEX SECONDARY INDEX NBTR ITERATOR