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

renameCollection 'c' op should restart initial sync upon application

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.2
    • Epic Link:
    • Sprint:
      Repl 2016-10-10
    • Case:

      Description

      This is to avoid the syncing node winding up with an incomplete set of data due to the inability of initial sync to properly handle renameCollection. See SERVER-4941 for more details.

        Attachments

          Issue Links

          is documented by

          Task - A task that needs to be done. DOCS-10763 Document that upgrading to 3.2.12 and 3.4.0 may cause initial sync to fail if collection renames are happening

          • Blocker - P1 - Blocks development and/or testing work, production could not run.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-25040 Initial syncing node maintains tmp collection from map reduce when primary has renamed it

          • Major - P3 - Major loss of function.
          • Closed
          is 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-29772 Provide option to 3.2 and 3.4 to allow initial sync to complete even when it encounters renameCollection entries

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

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: