[SERVER-27728] createIndex should add an entry in oplog even if the index exists Created: 18/Jan/17 Updated: 06/Dec/22 Resolved: 24/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Amar Hamzeh | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Sprint: | Repl 2017-01-23, Repl 2017-02-13 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
When an index is built in a rolling fashion (by taking nodes out of a replica set one by one and building the index on them) as described in Build Indexes on Replica Sets, an oplog entry never gets created and the index doesn't get created on the backup. There is currently no safe workaround to create such indexes on backup and the only available solution is a resync of backup which could be very long. Could we have a way to create an entry in oplog for indexes that already exist and have secondaries (including backup) only create that index if it's not already there? |
| Comments |
| Comment by Sara Williamson [ 24/Jun/19 ] |
|
We are working on other improvements to backup and the index building system, so rolling index builds will not be necessary in the future. Closing this as won't do. |
| Comment by Charlie Swanson [ 19/Jan/17 ] |
|
spencer, milkie, can you take a look and let us know what you think? Also, this may be better suited for the Storage backlog, feel free to move as appropriate. |