1 個回答
- 最新
- 最多得票
- 最多評論
0
Hello. Mongodump does not backup the actual indexes, just their definition, a piece of metadata that mongorestore will use to create the type of index on the specified field or fields. The recommended approach is exactly what you tried, pre-create the indexes on the empty collection, then restore with the --noIndexRestore option. This is also preferred because you get faster restore, creating an index on existing data is a single threaded operation which can take a long time on a large dataset. But restoring with a pre-existing index, along with the --numInsertionWorkersPerCollection option (match this with number vCPUs) will yield much faster restore times.
已回答 2 年前
相關內容
- 已提問 6 個月前
- AWS 官方已更新 8 個月前
- AWS 官方已更新 8 個月前