-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.6.9
-
Component/s: Index Maintenance
-
None
-
Fully Compatible
-
ALL
-
-
Quint Iteration 7
This could happen for example of you upgrade from 2.4 with a document that has a "key too large" and didn't run or fix db.upgradeCheckAllDBs().
Changing the document to make it grow causes the document to get cleared from the indexes. The document still exists but can't be found by _id.
This can have strange effects downstream and on secondaries. For example another document with the same _id can be created.
It also seems to result in the following on secondaries after a number of other operations:
[repl writer worker 3] ERROR: writer worker caught exception: :: caused by :: 10287 btree: key+recloc already in index on...