[SERVER-70220] onShardVersionMismatch should be onCollectionPlacementVersionMismatch Created: 05/Oct/22 Updated: 29/Oct/23 Resolved: 13/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2583-Milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-10-17 |
| Participants: |
| Description |
|
The onShardVersionMismatch function runs when the shard realizes it has stale information from the router. This function refreshes the information on the shard. For the index information, this can never happen because the shard is authoritative of the index information. Therefore, the onShardVersionMismatch function only needs to take in the chunk version. |
| Comments |
| Comment by Githook User [ 13/Oct/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |