[SERVER-58465] Fix the cleanup of the Routing Info in the rename operation Created: 13/Jul/21 Updated: 29/Oct/23 Resolved: 19/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.2, 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Sergi Mateo Bellido |
| 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 EMEA 2021-07-26 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 155 | ||||||||||||||||
| Description |
|
The problem is at the end of the rename operation, when we force a refresh on both collections: from and to. The issue is that the asynchronous work submitted by the the refresh of the from collection,which is a dropCollection, conflicts with the refresh of the to collection. You can find a detailed description of this problem here. As part of this work we should also remove this if-stmt. This code is not needed anymore since we already have a proper cleanup phase. |
| 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 [ 20/Jul/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: (cherry picked from commit 43072942ea3d57951ca1460b1d07acc436c15b5c) |
| Comment by Githook User [ 13/Jul/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |