[SERVER-44904] Startup recovery should not delete corrupt documents while rebuilding unfinished indexes Created: 02/Dec/19  Updated: 29/Oct/23  Resolved: 06/Jan/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.2.4, 4.3.3

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Eric Milkie
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-43882 Building indexes for startup recovery... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Execution Team 2020-01-13, Execution Team 2019-12-30
Participants:

 Description   

The --repair code deletes documents that it finds as corrupt. This code is shared with startup recovery when we rebuild unfinished indexes.

We should not delete corrupt document unless we are actively in --repair. We should fassert and crash immediately.



 Comments   
Comment by Githook User [ 29/Jan/20 ]

Author:

{'username': 'milkie', 'name': 'Eric Milkie', 'email': 'milkie@mongodb.com'}

Message: SERVER-44904 startup recovery should not delete corrupt docs while rebuilding unfinished indexes

cherry-picked from 12d44ec1d9a03ed3d0828096bb32de925235c447
Branch: v4.2
https://github.com/mongodb/mongo/commit/17dd13d9cdfd987cc0d2a1e143eaea3a5b7f8417

Comment by Githook User [ 06/Jan/20 ]

Author:

{'name': 'Eric Milkie', 'email': 'milkie@mongodb.com', 'username': 'milkie'}

Message: SERVER-44904 startup recovery should not delete corrupt docs while rebuilding unfinished indexes
Branch: master
https://github.com/mongodb/mongo/commit/12d44ec1d9a03ed3d0828096bb32de925235c447

Generated at Thu Feb 08 05:07:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.