Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Incomplete
-
3.0.5
-
None
-
None
-
ALL
-
Repl C (11/20/15), Repl D (12/11/15), Repl E (01/08/16), Repl F (01/29/16), Repl 10 (02/19/16), Repl 11 (03/11/16)
Description
We ran into a crash on 3.0.5 where the oplog was reported as going back in time, but the timestamps in the log match
replication oplog stream went back in time. previous timestamp: 55d25074:41 newest timestamp: 55d25074:41. Op being applied: { ts: Timestamp 1439846516000|65, h: 1280351009425609402, v: 2, op: "i", ns: "...", o: { ... }
|
Attachments
Issue Links
- is related to
-
-
- Closed
-