SERVER-59832 introduced a few changes to skip update/delete operations over orphan documents. In order to know if an operation affects an orphan document, we need the sharding ownership filter. The current implementation is asking for the ownership filter for each document but we know that if the collection lock is not yield it's going to be the same.
The goal of this task is to cache the ownership filter and only refresh it when we recover the lock (i.e. after a yield).
- is related to
-
SERVER-61767 Optimizing the new way of filtering writes over orphan documents
- Closed
- related to
-
SERVER-62279 Micro-optimize the skipWriteToOrphanDocument function in case of direct writes to shards
- Closed