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

replset6.js should await replication before checking that renameCollection replicated properly

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.6.0-rc3
    • None
    • Replication
    • None
    • Replication
    • Fully Compatible
    • ALL
    • 0

    Description

      replset6.js tests the replication of renameCollection commands across databases i.e.

      assert.commandWorked(admin.runCommand({
          renameCollection: "jstests_replsets_replset6_first.one",
          to: "jstests_replsets_replset6_second.two"
      }));
      

      renameCollection commands across databases are not atomic, and are comprised of several, individual oplog entries. The last oplog entry that gets logged is the drop of the source collection, and before that we rename the temp collection into its final destination. If there is a delay between the application of these ops, we might see the rename but not wait for the source collection to be dropped on secondary.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            william.schultz@mongodb.com William Schultz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: