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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.0-rc3
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Linked BF Score:
      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

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: