[SERVER-10480] Check for _id indexes on all collections at startup in replication mode Created: 09/Aug/13 Updated: 09/Aug/13 Resolved: 09/Aug/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
In the event of a suitably inopportune crash, a node might end up missing its _id indexes. (E.g., if you crash during a compact or a reIndex). This will lead to problems, probably crashes, when you turn the node back online as a secondary or a slave. Maybe the server should check for required indexes, and shut down gracefully with suitably informative log messages, when it starts up. |