[SERVER-55114] Bump the minor version of the newest chunk on change allowMigrations and reshardingFields Created: 10/Mar/21 Updated: 29/Oct/23 Resolved: 08/Jul/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: | Jordi Serra Torrens | Assignee: | Simon Gratzer (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2021-04-05, Sharding EMEA 2021-05-03, Sharding EMEA 2021-06-28, Sharding EMEA 2021-07-12 |
| Participants: |
| Description |
|
Currently, when changing the 'allowMigrations' or 'reshardingFIelds' field on config.collections, we are bumping the major version of a random chunk (or one random chunk per shard in resharding_coordinator). This can be optimized by bumping only the minor version of the newest chunk. This achieves the same guarantees of ending up with a new collection version, but it avoid the drawback of invalidating the versioning info of a shard. |
| 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 [ 08/Jul/21 ] |
|
Author: {'name': 'Simon Graetzer', 'email': 'simon.gratzer@mongodb.com'}Message: |
| Comment by Kaloian Manassiev [ 16/Mar/21 ] |
|
FYI, this will be repurposed to actually bump the chunk with the collection version instead of a random chunk. |