[SERVER-6626] Started receiving exception: btree: key+recloc already in index code:10287 - Created: 27/Jul/12 Updated: 14/Jan/14 Resolved: 22/Sep/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.0.6 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Eugene Shustef | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
After running without any problems, we started receiving "exception: btree: key+recloc already in index code:10287" error. The db log is attached. We are using 2.0.6. Some forums indicate that it might be just a debug statement and is harmless. Need confirmation. |
| Comments |
| Comment by random user [ 14/Jan/14 ] |
|
FYI: we had the very same issue, db.collection.reIndex() resolved it. |
| Comment by Scott Hernandez (Inactive) [ 27/Jul/12 ] |
|
Yes, this is benign but would you mind turning up logging verbosity and providing a little more logging to confirm the case this is happening for. Please set the logLevel to 5 till you get this message, and then turn it back to what it was: http://docs.mongodb.org/manual/reference/commands/#setParameter Are you building indexes or is this during normal writes? It looks like from the log that there is not index building going on. What version is this? A reIndex on AdsInSpaces should clean up these messages but let use wait till we see the logs to start that. |