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

Can't rollback dropCollection if new primary renamed the collection

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • None
    • None
    • Replication
    • None
    • Replication
    • Fully Compatible
    • ALL
    • 0

    Description

      Node A's oplog:
      optime 1: dropCollection foo

      Node B's oplog:
      optime 1': renameCollection foo -> bar

      When node A enters rollback it will try to "undo" the dropCollection by resyncing the foo collection from node B. But node B won't have any foo collection anymore since it has been renamed to bar. This will cause the nodes to silently be out of sync.

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. SERVER-29959 Fix renameCollection step in rollback via refetch

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-4941 collection rename may not replicate / clone properly during initial sync

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

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              mathias@mongodb.com Mathias Stearn
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: