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

[4.4] removing unindexed unique partial index entries generates write conflicts

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.29
    • Affects Version/s: 4.4.23
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Execution Team 2024-02-05

      In 4.4, removing index keys from a unique partial index that do not satisfy the partial filter may generate write conflicts for concurrent storage transactions that are also removing unindexed entries. This is largely due to existing logic intended to work with pre-4.2 background indexing operations, which is no longer a concern since background index builds were deprecated by hybrid index builds in 4.2.

      Some of this write conflicting behavior was removed in 5.0 as part of the cleanup in SERVER-51762.

      Prior to 4.4.23 (and SERVER-75922), this write conflicting behavior did not exist because we would return early on a partial filter miss.

            Assignee:
            louis.williams@mongodb.com Louis Williams
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: