[DOCS-2046] Shard maxSize does not use dataSize Created: 08/Oct/13 Updated: 11/Jan/17 Resolved: 09/Oct/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Hows | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: | |||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 10 years, 19 weeks ago | ||||
| Description |
|
Doc's say that MongoS will use dataSize in calculating shard size. Review of the code shows that we actually use the mapped value for that shard. This has implications if you delete documents to make space to free space to make a shard a viable candidate again. |
| Comments |
| Comment by auto [ 09/Oct/13 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Scott Hernandez (Inactive) [ 09/Oct/13 ] |
|
Also, added a note with Sam that local/admin dbs are included in mapped but probably not something you want in your specified maxSize number. The other note to add is that mapped represents the sum of all data files, not just the actual data you have, as David suggests above also. |