In a replica set if primary has problems writing to the oplog, for example because of corruption there, it still continues applying writes, but they never go to oplog. Thus they are not replicating. Additionally, once the problem is identified, there is no easy way to recover the applied data if it's not in the oplog.
Primary should abort if it encountered data access related assertions in
the oplog collection, including:
- invalid bsonobjsize
- delete bucket corrupted
- is related to
-
SERVER-6981 maxPasses assertion (on allocation failure) can make capped collection unreadable
- Closed
-
SERVER-17561 Fragmentation/non-linearity in mmapv1 capped collections
- Closed
-
SERVER-1558 Documents should write checksum on write, verify checksum on read
- Closed