[SERVER-7666] shard maxSize does not support draining well Created: 14/Nov/12 Updated: 11/Jul/16 Resolved: 20/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.2.1 |
| Fix Version/s: | 2.2.2, 2.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Minor Change | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
When a shard exceeds it's maxSize, by having more data mapped than is specified in config.shards::maxSize, the shard immediately starts draining as the first priority of the balancer. Mapped is a poor substitute in this case for shards. |
| Comments |
| Comment by auto [ 19/Nov/12 ] |
|
Author: {u'date': u'2012-11-14T23:20:24Z', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}Message: |
| Comment by auto [ 15/Nov/12 ] |
|
Author: {u'date': u'2012-11-15T17:38:52Z', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}Message: |