[SERVER-59788] Remove majorityAppliedDonorOpTime from recipientSyncData reply Created: 03/Sep/21 Updated: 27/Oct/23 Resolved: 19/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Serverless
|
||||
| Backport Requested: |
v5.1
|
||||
| Participants: | |||||
| Description |
|
When "protocol" is "slice merge", omit majorityAppliedDonorOpTime from the recipientSyncData reply. (It was introduced for Multitenant Migrations but not used, let's take the opportunity to clean it up.) |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 19/Oct/21 ] |
|
Nevermind, if we ever impl the optimization that Donor doesn't enter critical section until recipient is nearly caught up, this may be part of the mechanism. |