[SERVER-73441] Make sure shard key bounds are valid when committing `moveRange` Created: 30/Jan/23 Updated: 29/Oct/23 Resolved: 02/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 6.1.1, 6.0.4, 6.2.0-rc6 |
| Fix Version/s: | 6.3.0-rc0, 6.0.6 |
| 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: |
|
||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v6.2
|
||||||||||||||||
| Sprint: | Sharding EMEA 2023-02-06 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Before committing a chunk split, there is a check ensuring that the split point is a valid shard key. Since the auto-splitter has been eliminated and split points are now selected in the moveRange path, we must adapt the migration commit to also check that the new bounds are valid shard keys. |
| Comments |
| Comment by Githook User [ 30/Mar/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 01/Feb/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |