-
Type:
Bug
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Indexing, Replication
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Operating System:ALL
-
Backport Requested:v4.4, v4.2
-
Sprint:Repl 2020-07-27, Repl 2020-08-10
Normal replication recovery does, because shouldRelaxIndexConstraints returns "true" during STARTUP but shouldRelaxIndexConstraints returns "false" on a standalone, so recoverFromOplogAsStandalone does not.
- is related to
-
SERVER-49529 setTableLogging error at startup while creating index entry, in backup/restore test
-
- Closed
-
-
SERVER-49530 fix final index build phase for oplog recovery as a standalone mode
-
- Closed
-
-
SERVER-49924 Forward-port SERVER-49527 to master branch
-
- Closed
-