[SERVER-61938] ConfigureCollectionAutoSplit should check maxChunkSize in MB Created: 07/Dec/21  Updated: 29/Oct/23  Resolved: 26/Jan/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.3.0

Type: Task Priority: Major - P3
Reporter: Allison Easton Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-02-07
Participants:
Linked BF Score: 175

 Description   

TheĀ current check for max chunk size being within required bounds of 1MB to 1GB occurs after converting the max chunk size from the user to bytes from mb. This can cause an overflow without a proper error message if the user tries to input the max chunk size in bytes and ends up well beyond the limit of the command. We should check the bounds without the possibility of overflowing the int if the user input an invalid value.



 Comments   
Comment by Githook User [ 26/Jan/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-61938 ConfigureCollectionAutoSplit should check maxChunkSize in MB
Branch: master
https://github.com/mongodb/mongo/commit/066cadedbd1c49b552942230a8c364514bddee16

Generated at Thu Feb 08 05:53:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.