[SERVER-58771] Prevent querying config.chunks for the shard version during chunk migration Created: 22/Jul/21 Updated: 29/Oct/23 Resolved: 02/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2021-07-26, Sharding EMEA 2021-08-09 |
| Participants: |
| Description |
|
During chunk migration, versions are updated and then config.chunks is queried to try and return the latest version, including other simultaneous operations' updates to versions. This is not necessary since other operations may change the version while we are returning the version we have found, so we should avoid doing this extra work and return the version calculated from the migration. |
| 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 [ 02/Aug/21 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com'}Message: |