Currently, checking for whether a write operation already executed is done by traversing the transaction's oplog chain. This is very inefficient because it has to be done for every single write operation in order to even find out whether it needs to be retried or not.
In order to optimize this we will keep a cache of the last transaction's executed statements so they can be quickly checked.
- is duplicated by
-
SERVER-29978 op log observer ids system collections wrong
- Closed
- related to
-
SERVER-34178 Address lingering issues around TestData.excludedDBsFromDBHash
- Closed