[SERVER-54203] [causal consistency] Ensure copied keys have replicated to every donor node before tenant migration commits Created: 02/Feb/21 Updated: 29/Oct/23 Resolved: 08/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_alpha2, pm-1791_milestone-F | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2021-02-22, Sharding 2021-03-08, Sharding 2021-03-22 | ||||
| Participants: | |||||
| Description |
|
To ensure that a request signed with a cluster time by the recipient can be processed by a stale donor node, the external validation keys copied from the recipient to the donor must have replicated to each donor node and been cached in-memory before the migration commits. This can be done by waiting for the opTime of the last key insert to replicate to each voting node. Keys are copied at the beginning of a migration but this can be waited for near the end to improve performance. |
| Comments |
| Comment by Githook User [ 08/Mar/21 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |
| Comment by Jack Mulrow [ 02/Feb/21 ] |
|
Note that because of |