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

recovery oplog application updates multikey info on wrong collection

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.11, 4.4.10, 5.0.4, 5.1.0-rc0
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v5.0, v4.4, v4.2, v4.0
    • Sprint:
      Execution Team 2021-07-26
    • Linked BF Score:
      70

      Description

      The list of multikey updates is batched and keyed by collection name during oplog application OplogApplierImpl::_applyOplogBatch. In a recovery scenario where there may be multiple collections with the same name at different points in history, this mapping could be problematic. Downstream components such as the replication StorageInterface::setIndexIsMultikey() would be less prone to looking up the wrong collection from the collection catalog if given the collection UUID.

      A more robust way to maintain the multikey information to update would be to use the collection UUID rather than the namespace.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              benety.goh Benety Goh
              Reporter:
              benety.goh Benety Goh
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: