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

initial_sync_applier_error.js is now obsolete since initial sync supports renameCollection ops

    XMLWordPrintable

Details

    • Bug
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Replication
    • ALL

    Description

      The replsets/initial_sync_applier_error.js test tries to make sure that if initial sync fails on its first attempt due to the occurrence of a renameCollection operation on the sync source, it retries, and can succeed on a second attempt when no renameCollection operation occurs on the sync source. Now that we support renameCollection operations occurring on the sync source with the advent of collection UUIDs, this test is no longer testing what it originally was. If you observe a test run from the 3.6 branch, you can see that there are no failed initial sync attempts in the test. The first attempt just succeeds, since a renameCollection operation no longer causes an error during initial sync. Observe that there are two initial sync attempts from a 3.4 run of this test.

      Unless we want to test other kinds of errors during initial sync with this test, we should consider just removing it entirely, since renameCollection operations occurring during initial sync should now be tested by replsets/initial_sync_rename_collection.js.

      Attachments

        Issue Links

          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: