[SERVER-30832] Fix dbCheck behavior on rollback Created: 25/Aug/17 Updated: 05/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Kuehne | Assignee: | Evelyn Wu |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | neweng, pm-855-milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Sprint: | Repl 2024-02-19 | ||||||||
| Participants: | |||||||||
| Description |
|
Per the design doc, "If the secondary encounters dbChecks during recovery, a warning will be printed once to the system log and they will be ignored." The current behavior on rollback has not been tested, and it needs to be investigated and possibly fixed. Behavior during initial sync and recovery should also be investigated and possibly fixed. |