[SERVER-44708] Use lastCommittedOpTime in InvocationArgs as the clientsLastKnownCommittedOpTime in the next synthetic getMore request Created: 18/Nov/19 Updated: 06/Dec/22 Resolved: 17/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
| Comments |
| Comment by Lingzhi Deng [ 17/Dec/19 ] |
|
We will store the lastKnownCommittedOpTime (used in awaitData) in ClientCursor instead of using ReplyBuilderInterface::setNextInvocation implemented in |
| Comment by Lingzhi Deng [ 12/Dec/19 ] |
|
Given the implementation of |