-
Type:
Bug
-
Resolution:
Fixed
-
Priority:
Major - P3
-
-
Affects Version/s:
None
-
Component/s:
None
-
-
Fully Compatible
-
-
- Donor blocks writes for tenant1 at TS(100).
- New $changeStream aggregate comes in, initializes start time to current clusterTime, TS(300), returns empty batch with PBRT=TS(300)
- Migration commits. We advance the recipient clock to be at least blockTS , here is TS(100).
- On Recipient, new writes starts to come in and they writes at TS(200).
- Client issues CS getMore, gets ResumeTenantChangeStream, driver retries
- CS cursor resumes from the last token it saw, i.e. the PBRT at TS(300)
- Change stream resumes on recipient but skips all events that occurred between TS(100) and TS(300)