SERVER-134081ClosedFixed

Express user-index plan spins forever when an index entry references a missing record

h3. Problem {{LookupViaUserIndex::consumeOne}} loops forever when an index entry points to a record that does not exist. A single orphan index key turns any point query that takes the express user-index path into an unbounded CPU spin, bounded only by the operation's deadline. Observed on HELP-98643: a dev cluster on rc1018 ran at 100% CPU on the primary with read tickets fully consumed and roughly 350k/sec WiredTiger search calls sustaining a fraction of the normal throughput. h3. Mechanism

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix
9.1.0-rc09.1.0-rc10249.0.7
Components
Server components related to this issue

No components specified.

Labels
Tags and classification
bkp