[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: |
| Comment by auto [ 15/Aug/13 ] |
|
Author: {u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}Message: |