-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Storage 2017-07-31
-
0
The special logic of ignoring NamespaceNotFound during initial sync, where replaying the oplog should be idempotent, requires throwing exceptions for this error condition rather than returning a status.
- is related to
-
SERVER-30220 Lock correct nss for syncApply by UUID
- Closed
-
SERVER-30521 in syncApply, throw NamespaceNotFound rather than returning a status on missing database
- Closed
- related to
-
SERVER-33160 syncApply() treatment of delete operations on non-existent namespaces
- Closed