_logOplogEntriesForInvalidResults does not check if the oplog pointer is valid.
One case where this could happen was when running validate on a replica set member started as standalone. Even though the oplog existed, AutoGetOplog returned nullptr. This is being handled in SERVER-80789.
The other possibility is that the oplog doesn't actually exist because the node has always been standalone. We should check if it is possible to hit this code with timestamps in recordTimestamps (passing this check) in this case, and if so make the code resilient.
- is related to
-
SERVER-74642 Log additional information about the oplog entry that generated a document or index key when printing metadata
-
- Closed
-
- related to
-
SERVER-80789 Make AutoGetOplog behave consistently in replica set node started as standalone
-
- Closed
-