[SERVER-82071] Prevent users from specifying a lower max than min bound in merge chunks command Created: 11/Oct/23 Updated: 23/Nov/23 Resolved: 21/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Robert Sander |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | car-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Catalog and Routing
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | CAR Team 2023-11-13, CAR Team 2023-11-27 | ||||
| Participants: | |||||
| Linked BF Score: | 5 | ||||
| Story Points: | 1 | ||||
| Description |
|
In BF-30376, we saw that the collection_defragmentation test could, in very rare occasions, send a merge chunks command where the min bound was greater than the max bound. This wouldn't be a problem in production because this range wouldn't pass the checks we have that the range to be merged matches existing chunks. This can be fixed simply by checking in the shardsvrMergeChunks command if the max bound is less than the min bound, and throwing an error if so. |
| Comments |
| Comment by Githook User [ 21/Nov/23 ] |
|
Author: {'name': 'Robert Sander', 'email': 'robert.sander@mongodb.com', 'username': 'robsndr'}Message: |