-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
Repl 2020-10-05, Repl 2020-10-19
+ This ticket responsibility should also confirm that we report non-empty correct postBatchResumeToken (i.e., same value as reported for the previous batch) value in the user response for a batch size 0 caused because of find/getMore filters (i.e., data not matching the filter) or awaitDataTimeout has kicked in for that command.
- is depended on by
-
SERVER-51246 Write a noop into the oplog buffer after each batch to ensure tenant applier reaches stop timestamp
- Closed
- is related to
-
SERVER-49895 Expose getLatestOplogTimestamp() in aggregation cursor command responses on oplog
- Closed
-
SERVER-49896 Allow aggregate command to fail if minTs oplog cursor has fallen off the oplog
- Closed
-
SERVER-43270 Propagate $_resumeAfter from QueryRequest to CollectionScanParams in QueryPlannerAccess, CollectionScanNode, and buildStages()
- Closed
-
SERVER-43271 Return resumeToken in PlanExecutor and write jstests to verify resumeToken is returned and can be used to resume
- Closed