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

Can't rollback dropCollection if new primary renamed the collection

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Replication
    • Fully Compatible
    • ALL
    • 0

      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.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            mathias@mongodb.com Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: