[SERVER-26786] Calling repairDatabase on collections containing too-long index keys silently drops all indexes on non-MMAPv1 storage engines Created: 26/Oct/16 Updated: 06/Dec/22 Resolved: 24/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage, WiredTiger |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | repairDatabase | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
Affects WT on 3.0+ and InMemory on 3.2+. MMAPv1 is not affected. Collections containing long index keys that are inserted when failIndexKeyTooLong=false will have all indexes dropped after running repairDatabase if failIndexKeyTooLong is changed back to the default value of true. |
| Comments |
| Comment by Max Hirschhorn [ 06/May/17 ] |
|
This issue can manifest on any non-MMAPv1 storage engine (e.g. inMemory, ephemeralForTest) since all storage engines other than MMAPv1 call rebuildIndexesOnCollection(). |