[SERVER-44759] Leave index builds unfinished when aborted due to rollback or local failure Created: 21/Nov/19 Updated: 06/Dec/22 Resolved: 05/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
When a two-phase index build is torn down and the node is no longer primary, we remove the durable catalog entry using a ghost timestamp. This works, because this ghost write is always rolled back. We should leave the index build unfinished it is aborted due to rollback or local failure. By "local failure", I am referring to the case where an index build fails on a secondary, but not from an explicit abortIndexBuild oplog entry. |