[SERVER-59903] Do not wipe out renamed tags upon resuming the rename of sharded metadata Created: 13/Sep/21 Updated: 29/Oct/23 Resolved: 13/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 5.1.0, 5.0.2 |
| Fix Version/s: | 5.0.4, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| 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: | Sharding EMEA 2021-09-20 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 133 | ||||||||||||||||
| Description |
|
The updatesTag function is renaming the tags from the source to the target collection. This means that if a stepdown happens right after this call, the next time the operation will be resumed tags will be wiped out. The removeTagsMetadataFromConfig_notIdempotent call is not needed at all. Due to the original design of the rename operation, there is no need to delete the target collection tags since the rename will result in an early failure in case the target collection has tags. |
| 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 [ 21/Sep/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 13/Sep/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |