A user experienced a case where oplog entries were unexpectedly found at the beginning of the oplog after later records were truncated.
- causes
-
WT-3946 Truncate segfault with a NULL start cursor
- Closed
- is duplicated by
-
SERVER-31924 OplogStones can capture record ids to truncate out of order
- Closed