[SERVER-12850] Interrupted index builds are not resumed on restart (via createIndexes or ensureIndex) Created: 23/Feb/14 Updated: 10/Dec/14 Resolved: 24/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kamran K. | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Index builds that are started via the createIndexes command or the ensureIndex shell helper do not seem to resume after the server is shut down. JS tests are attached for both ensureIndex and createIndexes. Output:
I also noticed that there are a few IndexCatalog::createIndex() callers that use the default SHUTDOWN_CLEANUP behavior instead of specifying SHUTDOWN_LEAVE_DIRTY. Is that on purpose? — |
| Comments |
| Comment by Eric Milkie [ 24/Feb/14 ] |
|
The code as it stands only ensures interrupted index builds are restarted on SECONDARY's as part of replication. This is the only situation where restarting is required to maintain data integrity between PRIMARY and SECONDARY. |