[SERVER-57392] $_resumeAfter queries should not be resumable after tenant migration Created: 03/Jun/21 Updated: 29/Oct/23 Resolved: 07/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc1, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Pavithra Vetriselvan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_non-cloud-blocking | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v5.0
|
||||||||
| Sprint: | Repl 2021-06-14 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 132 | ||||||||
| Description |
|
The internal $_resumeAfter parameter to the find command takes a record ID which is specific to the node it is targeted to. We cannot automatically retarget these when a tenant migration commits, so perhaps we should return some error message other than TenantMigrationCommitted for them. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 07/Jun/21 ] |
|
Author: {'name': 'Pavi Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com', 'username': 'pvselvan'}Message: (cherry picked from commit 73143230ef6fdbfd4341cbc692bd582158990d19) |
| Comment by Githook User [ 07/Jun/21 ] |
|
Author: {'name': 'Pavi Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com', 'username': 'pvselvan'}Message: |
| Comment by Matthew Russotto [ 03/Jun/21 ] |
|
It looks like we currently still only use $_resumeAfter in initial sync, so perhaps we can just exclude the tests from tenant migration. |