[SERVER-5735] Add sh.set/getGlobalChunkSize() helper Created: 01/May/12 Updated: 09/May/12 Resolved: 01/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Shell |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Add a helper to update the config.settings namespace chunkSize field. – Might want to add a generic helper like sh.set/getSetting("key", val [, ns]) also – |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 01/May/12 ] |
|
See |
| Comment by Remon van Vliet [ 01/May/12 ] |
|
Since the original got closed : Hi, Well frankly I don't think MongoDB should even allow writes to the config database directly from the shell to begin with. There needs to be a way for mongo to error out if invalid settings are provided and you can't do that if you allow things like db.settings.update({_id:"chunkSize"}, {$set:{value:10}}). Basically all mutations to the config database collections should go through admin only shell commands that can do the appropriate checks and such. But that said I think it's still better to either error when it's already set or allow --chunkSize to basically always do the update mentioned above. I can't think of any arguments against that approach anyway. |