[SERVER-58068] Multi updates interrupted by a tenant migration should wait for the migration to complete Created: 24/Jun/21 Updated: 29/Oct/23 Resolved: 04/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.3, 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||||||
| Sprint: | Sharding 2021-07-12, Sharding 2021-07-26, Sharding 2021-08-09 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When a multi update is interrupted by a tenant migration, it is not safe to automatically retry since it is unknown which of the matching documents have been updated, so an error is returned to the user. This error is returned right away, so if the user chooses to retry they may hit the same error if the migration has not completed yet, which is a poor user experience. Instead, the multi update should wait for the migration to complete before returning. |
| 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 [ 04/Aug/21 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit a3d735522cd7af506ebe0d947c8e903b1c041b3e) |
| Comment by Githook User [ 04/Aug/21 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |