[DOCS-5629] Document disk space usage of sharding.archiveMovedChunks Created: 14/Jun/15 Updated: 11/Jan/17 Resolved: 22/Jun/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andre de Frere | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 8 years, 34 weeks, 2 days ago |
| Description |
|
sharding.archiveMovedChunks is enabled by default, and will write data to the file system for every move Chunk. This can consume a lot of disk space over time, and there is no automatic way to recover this space. The documentation should be updated to indicate that this usage is occurring. |
| Comments |
| Comment by Githook User [ 22/Jun/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 22/Jun/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |