-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
We should only replace invariants if the operation can report an error to the users cleanly and does not impact any subsequent operations. A few examples where this won't be the case is when the invariant it based on a state that is not limited to the current operation, like a lock state, collection catalog state etc. Additionally, if the invariant is to protect against a memory leak, we cannot replace it with a tassert.
- depends on
-
SERVER-71968 Investigate impact of invariants and tasserts on performance
- Closed
- is related to
-
SERVER-53968 Replace invariant with tassert in src/mongo/db/pipeline code
- Open