Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-10763

Document that upgrading to 3.2.12 and 3.4.0 may cause initial sync to fail if collection renames are happening

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Blocker - P1
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.12, 3.3.15
    • Component/s: manual, Rel Notes, Server
    • Labels:
      None
    • Last comment by Customer:
      true
    • Sprint:
      KANBAN BUCKET

      Description

      SERVER-26117 made it so that if initial sync encounters a renameCollection it will fail and restart, rather than proceeding and potentially corrupting data as it did in previous versions. Taht change is present starting in 3.2.12 and 3.4.0. We should make clear in the release notes for both that upgrading from 3.2.11- may cause initial syncs to start failing, especially if you are regularly using renameCollection or aggregation or mapReduce with $out (which performs a renameCollection internally)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              spencer Spencer Brody (Inactive)
              Participants:
              Last commenter:
              Backlog - Core Eng Program Management Team Backlog - Core Eng Program Management Team
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                3 years, 35 weeks, 1 day ago
                Date of 1st Reply: