[SERVER-38861] mongod --repair failed when key is too large Created: 05/Jan/19 Updated: 07/Jan/19 Resolved: 07/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.6.9 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Richard Xu | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
when running mongod --repair, the job aborted because "key too large to index, failing"
the log file is attached
could I use – mongod --setParameter failIndexKeyTooLong=false. --repair to fix it? |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 07/Jan/19 ] |
|
Hello Richard, Yes you may try using that parameter to try to complete the repair. If it still does not complete but you have access to the database, you may wish to drop your large index before attempting the repair again. If the repair still fails with that parameter, you may wish to restore from a backup or perform an initial sync if this node is a member of a replica set. I do not see anything to indicate a bug in the MongoDB server. For further MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources. Thank you, Danny |