[SERVER-74979] Return underlying error to user when an index build fails instead of IndexBuildAborted Created: 17/Mar/23 Updated: 18/Mar/23 Resolved: 17/Mar/23 |
|
| 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: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
We always return an IndexBuildAborted error code when an index build fails, which is not very descriptive, as the underlying problem might be that the index build was killed by a secondary due to a disk space issue. Surface the actual underlying error back to the createIndexes command. |