Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-76413

Optimize how update stage guards against the Halloween problem during multi updates

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Query Execution

      Currently, the stage pessimistically assumes that any secondary index change during multi-update might lead to the Halloween problem, even if the changed index isn't used to scan the records (see `_updatedRecordIds` in UpdateStage). In most cases it means that if an update affects a secondary index, record ids of all updated records are temporarily stored by the stage, which might be quite a lot for some kinds of updates.

       

            Assignee:
            backlog-query-execution Backlog - Query Execution
            Reporter:
            irina.yatsenko@mongodb.com Irina Yatsenko (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: