[SERVER-75984] Skip fassert on oplog application failures when restore flag is enabled Created: 11/Apr/23 Updated: 11/Apr/23 Resolved: 11/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 7.0.0-rc0, 6.0.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Moustafa Maher | Assignee: | Moustafa Maher |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Backport Requested: |
v7.0, v6.0
|
||||
| Sprint: | Repl 2023-04-17 | ||||
| Participants: | |||||
| Description |
|
As the first step of selective restore is to start the shard node as a replica set to do oplog application of the snapshot taken for restore, so for selective restore we might still have some oplogs referencing the unrestored collections which will fail with collection see this test. Selective restore process done with --restore flag is enabled, so we need to skip fassert on oplog application failures. This fix needs to be backported to 6.0 as selective restore got introduced in v6.0. |
| Comments |
| Comment by Moustafa Maher [ 11/Apr/23 ] |
|
It will be done as part of |