[SERVER-29197] Dangling index records when initial syncing node clones a capped collection that deletes records during collection scan Created: 15/May/17 Updated: 30/Oct/23 Resolved: 31/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 3.4.0, 3.4.1, 3.4.2, 3.4.3, 3.4.4 |
| Fix Version/s: | 3.4.6, 3.5.9 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||||||
| Sprint: | Storage 2017-05-29, Storage 2017-06-19 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
During an initial sync of a capped collection, the collection scan reads until it hits EOF. If records are inserted on the sync source during the collection scan, the scan may read more documents than the collection cap allows, which will result in records being deleted during the collection scan.
The collections in question will fail an index validation by the validate command. To repair this issue, run the reindex command. |
| Comments |
| Comment by Githook User [ 14/Jun/17 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: In initial sync, capped indexes were built along with regular indexes, as documents were inserted, using the MultiIndexBlock. (cherry picked from commit 3a3a6def395bab81e7545b15a93bee7799d9efb1) |
| Comment by Githook User [ 31/May/17 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: In initial sync, capped indexes were built along with regular indexes, as documents were inserted, using the MultiIndexBlock. |