-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2017-07-31, Repl 2017-08-21, Repl 2017-09-11
On a shard server it can be okay for the provided resumeToken to not exist in any oplog entry in certain scenarios.
- depends on
-
SERVER-29131 Support resumeAfter option to $changeNotication to control where to start returning notifications from, which always errors if no entry with the given resumeToken exists
- Closed
- is depended on by
-
SERVER-30198 Support resumeAfter option to $changeNotification in sharded clusters
- Closed