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

Provide option to 3.2 and 3.4 to allow initial sync to complete even when it encounters renameCollection entries

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.12, 3.4.0
    • Fix Version/s: 3.2.18, 3.4.10, 3.6.0-rc0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.4, v3.2
    • Sprint:
      Repl 2017-10-02
    • Case:

      Description

      Note that doing so may result in the node that was initial synced having incorrect or incomplete results for the collection that was renamed. See SERVER-4941 for more details.

        Attachments

          Issue Links

          related to

          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

          Task - A task that needs to be done. SERVER-26117 renameCollection 'c' op should restart initial sync upon application

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

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: