[DOCS-1775] Add some caution notes regarding creating a new hashed collection Created: 03/Aug/13 Updated: 11/Jan/17 Resolved: 28/Aug/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Zack Brown |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 10 years, 25 weeks ago | ||||
| Description |
|
When creating a new hashed collection, it will perform a presplit and move chunks to the other nodes. However, the move chunk command can fail for a couple of reasons: 1. Migration already in progress on the donor. As a result, the initial chunks will be unbalanced. This would mean that the balancer would have to move them later on, which is not ideal since moving chunks of a hashed collection is slow. So it would be recommended that the balancer is not running when creating a new hashed collection. |
| Comments |
| Comment by auto [ 28/Aug/13 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 28/Aug/13 ] |
|
Author: {u'username': u'Zackrobat', u'name': u'Zack Brown', u'email': u'zack.brown@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |