-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Replication
applyOperation_inlock() needs the collection lock held before calling the function, which may throw a NamespaceNotFound error. As a result, all callers have to handle NamespaceNotFound correctly for idempotency reasons. We should unify the logic.
- is related to
-
SERVER-73661 Improve applyOperation_inlock() API.
- Backlog
-
SERVER-34319 unify exception and error status handling in applyOplogBatchPerWorker
- Closed