[DOCS-7777] removeShard docs should note that only one shard can be in draining state Created: 29/Apr/16 Updated: 11/Jan/17 Resolved: 03/Jun/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Ramon Fernandez Marina | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 32 weeks, 6 days ago |
| Description |
|
The removeShard documentation (and possibly other related pages) should note that only one shard in a cluster can be in "draining" state at a given time. This is what happens if one tries to remove more than one shard in a cluster:
|
| Comments |
| Comment by Githook User [ 30/Jun/16 ] |
|
Author: {u'username': u'devkev', u'name': u'Kevin Pulo', u'email': u'kev@pulo.com.au'}Message: Mention that removeShard draining uses the balancer Follow-up from Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 13/Jun/16 ] |
|
Author: {u'username': u'rkumar-mongo', u'name': u'ravind', u'email': u'ravind.kumar@10gen.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |