[SERVER-22430] Validate the numInitialChunks parameter for 'shardcollection' earlier Created: 01/Feb/16  Updated: 19/Jun/18  Resolved: 23/Mar/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.4.0
Fix Version/s: 3.3.4

Type: Bug Priority: Major - P3
Reporter: Kamran K. Assignee: Dianna Hohensee (Inactive)
Resolution: Done Votes: 0
Labels: fuzzer-blacklist
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-35676 numInitialChunks Argument is Not Vali... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 12 (04/01/16)
Participants:

 Description   

ShardCollectionCmd::run relies on Chunk::multiSplit to validate that a chunk is not split into more than 8192 parts as part of a 'shardcollection' command:

    uassert(13333, "can't split a chunk in that many parts", m.size() < maxSplitPoints);

This check should occur earlier to prevent unnecessary work on the mongos process.



 Comments   
Comment by Githook User [ 23/Mar/16 ]

Author:

{u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}

Message: SERVER-22430 check numInitialChunks earlier in shardCollection so as to prevent potential OOM errors
Branch: master
https://github.com/mongodb/mongo/commit/4deaa5883717145719caaca5002aa3ce4bf1fc76

Generated at Thu Feb 08 04:00:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.