Tracking: MongoDB Tools Changes
(DOCS-4418)
|
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.15, mongodb-3.0 |
| Type: | Sub-task | Priority: | Major - P3 |
| Reporter: | Michael Paik | Assignee: | Allison Reinheimer Moore |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 9 years, 10 weeks, 6 days ago | ||||||||||||
| Description |
|
Document that mongodump and mongorestore now use a configurable number of threads to dump and restore. Probably need additional color on actual behavior (e.g. is the max one per collection, or does multithreading intelligently partition collections to dump/restore?) |
| Comments |
| Comment by Michael O'Brien [ 04/Dec/14 ] |
|
samk there is one flag related to parallelization in mognorestore that is not hidden: We can document that one - but the others are mostly "power user" flags which don't need to be documented. |