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

Do not assume FCV stability while filtering orphan documents in update/delete ops

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.3.0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding EMEA 2021-12-27
    • 152

      This issue was introduced in  SERVER-59832.

      The changes introduced in that commit assume that we have FCV stability during the execution of an update operation. However that's not true:  it could totally happen that we decide at this point that we are going to filter writes over orphan documents, but then when we re-evaluate the value of the feature flag in the getOwnershipFilter function we see that the feature flag isn't enabled anymore and hit the invariant.

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

              Created:
              Updated:
              Resolved: