[SERVER-9993] config upgrade does not succeed if shard maxSize is not of type long Created: 21/Jun/13  Updated: 11/Jul/16  Resolved: 15/Aug/13

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.4.4
Fix Version/s: 2.4.7, 2.5.2

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Shaun Verch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

Try a config upgrade with the maxSize field set to a floating point value in the config.shards collection.

Participants:

 Description   

... users may have specified this via the shell, and the field should probably be enforced as "numeric" not as a particular numeric type.



 Comments   
Comment by auto [ 02/Oct/13 ]

Author:

{u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}

Message: SERVER-9993 Accept any numeric type for the maxSize field in config.shards
Branch: v2.4
https://github.com/mongodb/mongo/commit/6c0b71b3845dddb48a30c9ad63627cf0af8c2356

Comment by auto [ 15/Aug/13 ]

Author:

{u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}

Message: SERVER-9993 Accept any numeric type for the maxSize field in config.shards
Branch: master
https://github.com/mongodb/mongo/commit/d37eb1a01e0947b689d232430eac782a41e89ae0

Generated at Thu Feb 08 03:21:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.