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

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.7.0
    • Sharding
    • Fully Compatible
    • 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

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32198 Missing collection metadata on the shard implies both UNSHARDED and "metadata not loaded yet"

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

          Task - A task that needs to be done. SERVER-48326 Complete TODO listed in SERVER-47701

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

          Activity

            People

              marcos.grillo@mongodb.com Marcos José Grillo Ramirez
              garaudy.etienne@mongodb.com Garaudy Etienne
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: