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

rolling back a collection drop with long index names may not restore all the indexes

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc1
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2017-10-23

      In SERVER-29747, we drop indexes with names that are too long for the MMAPv1 index catalog before renaming the collection to the system.drop namespace. In a mixed cluster with a WiredTiger primary and a MMAPv1 secondary, the collection drop on the secondary would be executed with the indexes (with long index names), dropped implicitly. In the event of a rollback on the MMAPv1 secondary, these dropped indexes will not be restored.

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: