-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.5.1
-
Component/s: Replication
-
None
-
Replication
-
ALL
-
-
Repl 2024-06-10
-
50
When we come out of rollbackViaRefetch, we may remain in RECOVERING state until we have applied oplog entries up to our minValid optime. Our current state post rollback may not be consistent with the oplog, so we must relax constraints during oplog application. Currently, the OplogApplier used for oplog application in BackgroundSync always runs in application mode kSecondary. We need to make sure it uses mode kRecovering when applying ops during RECOVERING post rollback since now we enforce constraints whenever we are applying in mode kSecondary (SERVER-21700).
- is caused by
-
SERVER-21700 Do not relax constraints during steady state replication
- Closed
- is duplicated by
-
SERVER-84788 Remove RollbackViaRefetch method
- Closed
- is related to
-
SERVER-47053 Relax oplog application constraints in EMRC=false variants
- Closed