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

Cache the sharding ownership filter in the update/delete stage

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 5.3.0
    • 5.3.0
    • Sharding
    • None
    • Fully Compatible
    • Sharding EMEA 2022-01-10, Sharding EMEA 2022-01-24, Sharding EMEA 2022-02-07
    • 135

    Description

      SERVER-59832 introduced a few changes to skip update/delete operations over orphan documents. In order to know if an operation affects an orphan document, we need the sharding ownership filter. The current implementation is asking for the ownership filter for each document but we know that if the collection lock is not yield it's going to be the same.

      The goal of this task is to cache the ownership filter and only refresh it when we recover the lock (i.e. after a yield).

      Attachments

        Issue Links

          Activity

            People

              sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
              sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: