SERVER-32156Needs Scheduling

Linear field lookup in update subsystem can lead to an individual update having quadratic time complexity

We had some erroneous data enter our system and get written to a mongo collection. It resulted in a document containing over 600,000 attributes in it. When a find or update was attempted on this document the mongo server master went to 200% CPU and all other work ground to a halt. We attempted to kill the operation but it would not stop. It seemed that the operation was holding locks and was not yielding. Here is a sample of what the currentOp() looked like for the operation: Note that we

Affected Versions
Versions known to exhibit this issue
3.2.163.4.63.6.0
Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue
Performance
Labels
Tags and classification
query-44-grooming