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

recovery oplog application updates multikey info on wrong collection

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.11, 4.4.10, 5.0.4, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible
    • ALL
    • v5.0, v4.4, v4.2, v4.0
    • Execution Team 2021-07-26
    • 70

      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.

            benety.goh@mongodb.com Benety Goh
            benety.goh@mongodb.com Benety Goh
            0 Vote for this issue
            5 Start watching this issue