[SERVER-8238] Log warning if collections are missing _id index Created: 18/Jan/13 Updated: 11/Jul/16 Resolved: 26/Aug/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.3 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Do this only if replication is enabled. This is very hard to diagnose and track down and can be a cause of significant performance issues. Log the collection and get a doc to see if there is a _id in it. This can be checked at startup while we're doing the other index checks. |
| Comments |
| Comment by auto [ 26/Aug/13 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |
| Comment by Richard Kreuter (Inactive) [ 09/Aug/13 ] |
|
Would also be good for the server to shut down promptly in this case. |