Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.9.0
Affects Version/s: None
Component/s: Replication
Labels:
- pm-1791_milestone-B

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Repl 2020-10-05, Repl 2020-10-19
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

+ 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

Assignee:: Judah Schvimer
Reporter:: Suganthi Mani
Participants:: Githook User, Judah Schvimer, Suganthi Mani
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Sep 29 2020 07:55:34 PM UTC
Updated:: Oct 29 2023 10:02:38 PM UTC
Resolved:: Oct 13 2020 09:41:06 PM UTC
Confidence Status Last Update:: 29/Sep/20 9:25 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates