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

Multikey indexes can be mistakenly treated as non-multikey indexes

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Server Triage

      Issue Status as of July 15, 2024

      ISSUE DESCRIPTION

      This ticket consolidates information about a set of concurrency bugs that could result in the multikey metadata for an index being set incorrectly.
      As a result, queries against multikey indexes can mistakenly treat the multikey index as a non-multikey index, and return query results containing individual elements rather than arrays containing those elements.

      DIAGNOSIS AND IMPACT

      The above tickets present similarly and their symptoms are not readily distinguishable from one another. They are identified by validate failures including messages like:

      • "... multikey paths do not cover a document ..."
      • "... is not multikey but document with RecordId ..."
      • "... multikey paths do not cover a document with RecordId ..."

      REMEDIATION AND WORKAROUNDS

      • The recommended solution is to perform a logical initial sync on the affected node(s).
      • The sync source is irrelevant; the index will be successfully rebuilt regardless of your selection.

            Assignee:
            Unassigned Unassigned
            Reporter:
            chris.kelly@mongodb.com Chris Kelly
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: