-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.4.0
-
Component/s: None
-
None
-
Storage Engines
-
Fully Compatible
-
ALL
-
Execution Team 2021-06-28, Execution Team 2021-07-12, Execution Team 2021-08-23, Execution Team 2021-09-06
-
(copied to CRM)
For unknown reasons, TTL deletes that use a descending index (e.g. {lastUse: -1}) take at least an order of magnitude more time than deletes on an equivalent, ascending index (e.g.{lastUse: 1}).
Investigate and attempt to fix this problem.
- depends on
-
SERVER-55750 Enable Feature flag for PM-2227
- Closed
-
SERVER-65528 Use range bounded cursors for restoring index cursors after yielding
- Closed
- is related to
-
SERVER-69659 Test performance of restoring index cursors during TTL deletes
- Open
- related to
-
SERVER-57221 Inconsistent delete performance on collections with multiple secondary indexes on same key
- Closed
-
SERVER-56509 Wrap unique index insertion _keyExists call in a WT cursor reconfigure.
- Closed