[SERVER-20222] Index rebuilding on secondary during initial resync is not done in parallel for multiple collections or DBs Created: 31/Aug/15 Updated: 26/Sep/15 Resolved: 26/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Replication, WiredTiger |
| Affects Version/s: | 3.0.5 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Baruch Oxman | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Some setup info: When running an initial resync for an instance that contains 1000+ DBs, each with ~100 collections, with over 1000 indexes overall (per-db), the resync process is very slow. Specifically, the index creation process is very slow. It would be wise to rebuild many indexes in parallel, to fully utilize the available resources and shorten the resync process. |
| Comments |
| Comment by Baruch Oxman [ 01/Sep/15 ] |
|
Thanks Dan, An additional improvement suggestions:
|
| Comment by Daniel Pasette (Inactive) [ 01/Sep/15 ] |
|
Hi Baruch, There are a number of ways we're planning to improve the speed of initial sync. Here's a few to watch: |