[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: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| 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 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: |