[SERVER-14737] Initial sync uses background index building Created: 31/Jul/14 Updated: 20/Apr/22 Resolved: 13/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.6.3 |
| Fix Version/s: | 2.7.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Ryder (Inactive) | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | cap-ticket-needed | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Steps To Reproduce: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| Description |
|
When a node is performing initial sync in 2.6.3 it will build indexes using the method specified by the original index build command even though the node does not become a viable SECONDARY until the index builds are complete. Eg.
I would expect the node to either build indexes using the foreground process or allow the node to enter SECONDARY status. |
| Comments |
| Comment by Githook User [ 13/Aug/14 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: All index builds now go through the MultiIndexBuilder as its API was already
|
| Comment by Eric Milkie [ 31/Jul/14 ] |
|
The correct behavior for initial sync will be to build all indexes in the foreground and in a bulk operation that reduces multiple scans across the data. |
| Comment by Eric Milkie [ 31/Jul/14 ] |
|
I believe it may be true that the cloner builds indexes with {background:true} as background indexes. The cloner is used in initial syncing and to implement the various clone/copy collection/DB commands. |