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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.0-rc1
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl 2017-10-23

      Description

      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.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31060 Two phase drops with too long MMAPv1 index names must generate dropIndexes operations before drop operation

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-29747 Two phase drops: drop indexes before renaming collections if the rename will make the index name too long

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: