[SERVER-54703] Forced re-configs will restart the collection scan phase of index builds Created: 22/Feb/21  Updated: 29/Oct/23  Resolved: 21/Apr/21

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Replication
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File repro.js    
Issue Links:
Backports
Related
is related to SERVER-53953 Fix invariant failure when downgradin... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Execution Team 2021-04-19, Execution Team 2021-05-03
Participants:

 Description   

Forced reconfigs will bypass doing a noop write while also clearing the committed snapshot (as detailed in SERVER-54389).

Index builds use a read concern majority cursor for the collection scan. If a forced reconfig clears the committed snapshot while there's an index build in progress, the index build will invariant.



 Comments   
Comment by Githook User [ 21/Apr/21 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-54703 Forced re-configs will restart the collection scan phase of index builds
Branch: master
https://github.com/mongodb/mongo/commit/b2c065bd6a8107a8440de1eb3e1fd43538188493

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