[SERVER-13240] CreateIndexes: report per index errors/status Created: 17/Mar/14 Updated: 06/Dec/22 Resolved: 14/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Index Maintenance |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently if an error occurs on the Nth index (or all but one) it is unclear what has been done and what order the indexes are created, and which one is the error. Also, there is no indication if it failed at the first problem, or if there was more than one error, and if more than one, which one was reported. We should report information like the write commands and include error information about each index, and build all indexes we can. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 14/Jun/19 ] |
|
A createIndexes cmd that is given several indexes to build will build all or none, for the last few server versions at least. And we now return error msgs including which index spec was not valid ( |