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

XMLWordPrintableJSON

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

      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
              Reporter:
              Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: