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

Prevent multi-false UpdateStage/DeleteStage from provoking yield after having already written

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding EMEA 2023-07-10
    • 140

      SERVER-77116 is built on the idea that multi=false updates/deletes should not yield after having performed one write, since upon restore the sharding placement could have changed and that would bubble up a StaleConfig exception. However, SERVER-77116 missed one case: After performing the writes, UpdateStage/DeleteStage restore their children stages, which can potentially fail due to WT failing with a WCE which needs to be handled by yielding. This undermines SERVER-77116. To solve this, we can skip restoring the children stages once UpdateStage/DeleteStage has reached EOF, since the children stages won't be used anymore.

            Assignee:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Reporter:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: