-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.2.0
-
Component/s: Replication
-
Fully Compatible
If the upstream server incorrectly returns documents from an oplog tailing query which are not in the correct order, monotonically increase by the "ts" field (time basically), then the client (replica) should treat that as a query error and issue a new query.
Getting idempotent oplog entries out of order is incorrect behavior from the sync source (upstream server).
- is related to
-
SERVER-21867 WiredTiger oplog cursor can return repeated segments
- Closed
-
SERVER-21962 Add testing hook for detecting anomalous log entries to resmoke.py
- Closed