[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:
Backports
Related
is related to SERVER-12536 Only allow shard key types which can ... Backlog
is related to SERVER-73537 `autoSplitVector` must not return inv... Blocked
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: SERVER-73441 Make sure shard key bounds are valid when committing `moveRange`
Branch: v6.0
https://github.com/mongodb/mongo/commit/a4b93b5a2cb6fd6118efcc3cad4aec9f10c17209

Comment by Githook User [ 01/Feb/23 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-73441 Make sure shard key bounds are valid when committing `moveRange`
Branch: master
https://github.com/mongodb/mongo/commit/8a1ce1c8c1b902c60b421e14feca681bee735547

Generated at Thu Feb 08 06:24:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.