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

Ensure the steps for upgrading Replica Set to a Sharded Cluster do not incur any application downtime

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: Sharding
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 2020-05-04, Sharding 2020-05-18, Sharding 2020-06-01

      Description

      When customers transition from replicat set to a sharded cluster, before sharding any collections, they access shards directly. Let's ensure that they're still able to do so once we block the ability to write directly to shards.

      Testing Steps: https://jira.mongodb.org/browse/DOCSP-10021

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marcos.grillo Marcos José Grillo Ramirez
              Reporter:
              garaudy.etienne Garaudy Etienne
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: