[SERVER-6840] Auto build compound index without the define Created: 24/Aug/12 Updated: 08/Mar/13 Resolved: 10/Oct/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.0.5 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Chris Duong | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | indexing, query | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Amazon Linux 64bit |
||
| Participants: |
| Description |
|
While my clients query with compound field like {a: x, b: y}, my mongodb server automatically started to build compound index {a: 1, b: 1} at the same. Then my server became unresponsive for a while, which made my clients get null result when querying. ", happen very frequently; although I don't define that compound index. . |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 24/Aug/12 ] |
|
The system will not automatically define or create indexes. Please check your application code and all users who have access to the system to find the cause. The log line where the index build starts will be prefixed by the connection-id which you can look through the logs for to see which client is issueing the command which creates the index. |