DOCS-15138 enableSharding (#1040)

kennethdyer · jeff-allen-mongo · ianf-mongodb · web-flow · commit 3e13f8614b44 · 2022-05-16T12:21:13.000-04:00
* DOCS-15138 Adds versionchanged notice to reference page * (DOCS-15177): Add count to stable API v1 (#1015) * (DOCSP-21679): stage stable api updates for count add 6.0 release notes add stable api changelog remove extra text updates per review feedback re-stage re-stage add footnotes to table adjust table widths table widths tweak header copy adding command specific section to changelog formatting formatting * remove count migration example * remove list of supported commands * tweak * add link to stable api changelog from release notes * clarify actor * add stable API ref * apply copy review suggestion * wording * DOCS-15267 Add release date for v5.0.8 (#1018) * DOCS-15267 * Update 5.0.txt * DOCSP-22186-namespace-content-addition (#1017) * DOCSP-22186-namespace-content-addition * DOCSP-22186-namespace-content-addition * DOCSP-22186-namespace-content-addition * DOCSP-22186-namespace-content-addition * DOCSP-22186-namespace-content-addition Co-authored-by: jason-price-mongodb <jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com> * DOCS-15138 Refactors enableSharding definition * DOCS-15138 Refactor enablesharding definition * DOCS-15138 Refactor enablesharding definition * DOCS-15138 Refactor enablesharding definition * DOCS-15138 Refactor enablesharding definition * DOCS-15138 Sharding procedure update * DOCS-15138 Updates steps * DOCS-15138 Removes enableSharding step * DOCS-15138 Removes enableSharding step * DOCS-15138 Removes enableSharding step * DOCS-15138 Fixes broken links * DOCS-15138 Fixes per Joe * DOCS-15138 Fixes per Joe * DOCS-15138 Fixes per Tomasso Tocci Co-authored-by: jeff-allen-mongo <jeffrey.allen@10gen.com> Co-authored-by: ianf-mongodb <85948430+ianf-mongodb@users.noreply.github.com> Co-authored-by: jason-price-mongodb <69260375+jason-price-mongodb@users.noreply.github.com> Co-authored-by: jason-price-mongodb <jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com>
diff --git a/source/core/sharding-shard-a-collection.txt b/source/core/sharding-shard-a-collection.txt
@@ -12,11 +12,6 @@ Shard a Collection
    :depth: 2
    :class: singlecol
 
-.. note::
-
-   To shard a collection, you need to :ref:`enable sharding
-   <sharding-setup-enable-sharding>`.
-
 To shard a collection, you must specify the full namespace of the
 collection that you want to shard and the shard key. You can use the
 :binary:`~bin.mongosh` method :method:`sh.shardCollection()` to
diff --git a/source/core/timeseries/timeseries-shard-collection.txt b/source/core/timeseries/timeseries-shard-collection.txt
@@ -27,10 +27,8 @@ Prerequisites
 
 To shard a time series collection, first:
 
-1. :ref:`Deploy a sharded cluster <sharding-procedure-setup>` to host
-   the database that contains your time series collection.
-
-#. :ref:`Enable sharding for your database <sharding-setup-enable-sharding>`.
+- :ref:`Deploy a sharded cluster <sharding-procedure-setup>` to host
+  the database that contains your time series collection.
 
 Procedure
 ---------
diff --git a/source/includes/steps-convert-replica-set-enable-sharding.yaml b/source/includes/steps-convert-replica-set-enable-sharding.yaml
@@ -4,34 +4,9 @@ source:
   ref: connect-mongos
 ---
 title:
-  text: Enable sharding for a database.
-  character: "`"
-stepnum: 2
-ref: enable-sharding-db-level
-pre: |
-  Before you can shard a collection, you must first enable sharding
-  for the collection's database. Enabling sharding for a database does not
-  redistribute data but makes it possible to shard the collections in
-  that database.
-action:
-  - pre: |
-      The following operation enables
-      sharding on the ``test`` database:
-    language: sh
-    code: |
-      sh.enableSharding( "test" )
-  - pre: |
-      .. include:: /includes/extracts/mongos-operations-wc-enable-sharding.rst
-
-      The operation returns the status of the operation:
-    language: sh
-    code: |
-      { "ok" : 1 }
----
-title: 
   text: Determine the shard key.
   character: "`"
-stepnum: 3
+stepnum: 2
 ref: determine-shard-key
 content: |
   For the collection to shard, determine the shard key. The :ref:`shard
@@ -45,14 +20,14 @@ content: |
   - allow for effective distribution of activity among shards.
 
   For more information, see :ref:`sharding-shard-key-selection`.
-  
+
   This procedure will use the ``number`` field as the shard key for
   ``test_collection``.
 ---
-title: 
+title:
   text: Create an index on the shard key.
   character: "`"
-stepnum: 4
+stepnum: 3
 ref: enable-sharding-create-index
 pre: |
     Before sharding a non-empty collection, create an :doc:`index on
@@ -63,10 +38,10 @@ action:
     use test
     db.test_collection.createIndex( { number : 1 } )
 ---
-title: 
+title:
   text: Shard the collection.
   character: "`"
-stepnum: 5
+stepnum: 4
 ref: enable-sharding-collection
 action:
   - pre: |
@@ -77,7 +52,7 @@ action:
       use test
       sh.shardCollection( "test.test_collection", { "number" : 1 } )
   - pre: |
-  
+
       .. include:: /includes/extracts/mongos-operations-wc-shard-collection.rst
 
       The method returns the status of the operation:
@@ -93,7 +68,7 @@ post: |
 title: 
   text: Confirm the shard is balancing.
   character: "`"
-stepnum: 6
+stepnum: 5
 ref: enable-sharding-confirm
 action:
   - pre: |
diff --git a/source/includes/steps-shard-a-collection-ranged.yaml b/source/includes/steps-shard-a-collection-ranged.yaml
@@ -28,31 +28,6 @@ action:
     code: |
       mongosh --host <hostname> --port <port> --username <user> --password <pass> --authenticationDatabase 'admin'
 ---
-title: "Enable Sharding on the Database"
-level: 4
-ref: shard-database
-pre: |
-  Issue the :method:`sh.enableSharding()` method, specifying the name of the 
-  target database:
-
-action:
-  - pre: |
-    language: javascript
-    code: |
-      sh.enableSharding("<database>")
-  - pre: |
-      Optionally, enable sharding using the :dbcommand:`enableSharding` 
-      database command
-    language: javascript
-    code: |
-      db.runCommand( { enableSharding : <database> } )
-post: |
-  .. include:: /includes/extracts/mongos-operations-wc-enable-sharding.rst
-
-  
-  Enabling sharding on a database does *not* begin the sharding process. 
-  It only allows for collections within that database to be sharded.
----
 title: "Determine the Shard Key"
 level: 4
 ref: select-shard-key
diff --git a/source/includes/steps-shard-existing-tsc.yaml b/source/includes/steps-shard-existing-tsc.yaml
@@ -32,9 +32,7 @@ content: |
             "minCompatibleVersion" : 5,
             "currentVersion" : 6,
       ...
-   
-   If ``sh.status()`` returns ``This db does not have sharding enabled.``, 
-   :ref:`enable sharding <sharding-setup-enable-sharding>`.
+
 ---
 title: Shard the collection.
 ref: new-sharded-tsc-create
diff --git a/source/includes/steps-shard-new-tsc.yaml b/source/includes/steps-shard-new-tsc.yaml
@@ -33,9 +33,7 @@ content: |
             "minCompatibleVersion" : 5,
             "currentVersion" : 6,
       ...
-   
-   If ``sh.status()`` returns ``This db does not have sharding enabled.``, 
-   :ref:`enable sharding <sharding-setup-enable-sharding>`.
+
 ---
 title: Create the collection.
 ref: new-sharded-tsc-create
diff --git a/source/includes/steps-zones-initial-chunk-distribution-compound-hashed-non-prefix.yaml b/source/includes/steps-zones-initial-chunk-distribution-compound-hashed-non-prefix.yaml
@@ -71,22 +71,6 @@ content: |
      ``"facility" : "FacilityBaker"`` and all possible values of 
      ``_id``.
 
----
-title: "Enable Sharding for the Database"
-level: 4
-optional: true
-ref: initial-chunk-distribution-create-zones-enable-sharding
-content: |
-
-   Skip this step if you already enabled sharding on the database.
-
-   Use :method:`sh.enableSharding()` to enable sharding for the
-   database:
-
-   .. code-block:: javascript
-
-      sh.enableSharding("examples")
-
 ---
 title: "Shard the Collection"
 level: 4
diff --git a/source/includes/steps-zones-initial-chunk-distribution-compound-hashed-prefix.yaml b/source/includes/steps-zones-initial-chunk-distribution-compound-hashed-prefix.yaml
@@ -33,22 +33,6 @@ content: |
          "FacilityAlpha"
       );
 
----
-title: "Enable Sharding for the Database"
-level: 4
-optional: true
-ref: initial-chunk-distribution-create-zones-enable-sharding
-content: |
-
-   Skip this step if you already enabled sharding on the database.
-
-   Use :method:`sh.enableSharding()` to enable sharding for the
-   database:
-
-   .. code-block:: javascript
-
-      sh.enableSharding("examples")
-
 ---
 title: "Shard the Collection"
 level: 4
diff --git a/source/includes/steps-zones-initial-chunk-distribution-single-compound.yaml b/source/includes/steps-zones-initial-chunk-distribution-single-compound.yaml
@@ -35,22 +35,6 @@ content: |
           "DC2"
       );
 
----
-title: "Enable Sharding for the Database"
-level: 4
-optional: true
-ref: initial-chunk-distribution-create-zones-enable-sharding
-content: |
-
-   Skip this step if you already enabled sharding on the database.
-
-   Use :method:`sh.enableSharding()` to enable sharding for the
-   database:
-
-   .. code-block:: javascript
-
-      sh.enableSharding("exampledb")
-
 ---
 title: "Shard the Collection"
 level: 4
diff --git a/source/reference/command.txt b/source/reference/command.txt
@@ -480,7 +480,7 @@ Sharding Commands
 
    * - :dbcommand:`enableSharding`
 
-     - Enables sharding on a specific database.
+     - Creates a database.
 
    * - :dbcommand:`flushRouterConfig`
 
diff --git a/source/reference/command/enableSharding.txt b/source/reference/command/enableSharding.txt
@@ -15,28 +15,31 @@ Definition
 
 .. dbcommand:: enableSharding
 
-   The :dbcommand:`enableSharding` command enables :doc:`sharding
-   </sharding>` on the specified database. Once you enabled sharding
-   for a database, you can use the :dbcommand:`shardCollection` command
-   to shard collections in that database.
+   .. note::
+
+      .. versionchanged:: 6.0
+
+      Starting in MongoDB 6.0, this command is **not** required to
+      :doc:`shard </sharding>` a collection.
+
+   The :dbcommand:`enableSharding` command explicitly creates a database.
 
    The :binary:`~bin.mongosh` method :method:`sh.enableSharding()`
    wraps the :dbcommand:`enableSharding` command.
-  
+
 Syntax
 ------
 
 The :dbcommand:`enableSharding` command has the following syntax:
 
-- *Recommended*.  Specify just the database for which to enable sharding.
+- *Recommended*.  Specify the database to create:
 
   .. code-block:: javascript
 
      db.adminCommand( { 
         enableSharding: "<database name>"
      } )
 
-
 - Optionally, starting in MongoDB 4.2.2 (and 4.0.14), you can
   include the primary shard specification in the command, although this
   is not recommended:
@@ -48,7 +51,7 @@ The :dbcommand:`enableSharding` command has the following syntax:
         primaryShard: "<shard name>"  // Available starting in MongoDB 4.2.2 (and 4.0.14)
      } )
 
-You can only run :dbcommand:`enableSharding` in the ``admin`` database
+You can only run the :dbcommand:`enableSharding` command on the ``admin`` database
 from a :binary:`~bin.mongos` instance.
 
 Fields
@@ -70,7 +73,8 @@ The command takes the following fields:
 
      - .. _cmd-enableSharding-db:
 
-       The database for which you wish to enable sharding.
+       The database you want to use.  The database is created if it
+       does not exist.
 
    * - :ref:`primaryShard <cmd-enableSharding-primaryShard>`
 
@@ -123,14 +127,12 @@ shard for a database, use :dbcommand:`movePrimary` instead.
 Example
 -------
 
-The following command, run from a :binary:`~bin.mongos`, enables
-sharding for the ``test`` database:
+The following command, run from a :binary:`~bin.mongos`, creates the 
+the ``shardTest`` database:
 
 .. code-block:: javascript
 
-   db.adminCommand( { enableSharding: "test" } )
-
-To verify, run :method:`sh.status()`.
+   db.adminCommand( { enableSharding: "shardTest" } )
 
 .. seealso::
 
diff --git a/source/reference/command/nav-sharding.txt b/source/reference/command/nav-sharding.txt
@@ -88,7 +88,7 @@ Sharding Commands
 
    * - :dbcommand:`enableSharding`
 
-     - Enables sharding on a specific database.
+     - Creates a database.
 
    * - :dbcommand:`flushRouterConfig`
 
diff --git a/source/reference/command/refineCollectionShardKey.txt b/source/reference/command/refineCollectionShardKey.txt
@@ -194,12 +194,6 @@ Examples
 
 To set up the example in the ``test`` database:
 
-a. Enable sharding on the database, if sharding is not already enabled:
-
-   .. code-block:: javascript
-
-      sh.enableSharding("test")
-
 #. Use following :dbcommand:`shardCollection` operation to shard the
    ``orders`` collection in the ``test`` database. The operation
    uses the ``customer_id`` field as the initial :ref:`shard key
@@ -248,12 +242,6 @@ Collection with non-``simple`` Collation
 
 To set up the example in the ``test`` database:
 
-a. Enable sharding on the database, if sharding is not already enabled:
-
-   .. code-block:: javascript
-
-      sh.enableSharding("test")
-
 #. Create the ``cafés`` collection in the ``test`` database,
    specifying French ``fr`` as the default :doc:`collation </reference/collation>`.
 
diff --git a/source/reference/command/setDefaultRWConcern.txt b/source/reference/command/setDefaultRWConcern.txt
@@ -220,8 +220,8 @@ Sharding Administrative Commands Override Write Concern Settings
 
 Sharding administrative commands that perform write operations on the
 :ref:`config server <sharding-config-server>`, such as the
-:dbcommand:`enableSharding` or :dbcommand:`addShard` commands, have
-specific behavior with global default write concern settings:
+:dbcommand:`enableSharding` or :dbcommand:`addShard` commands,
+have specific behavior with global default write concern settings:
 
 - The commands use :writeconcern:`"majority"` regardless of the 
   configured global default write concern.
diff --git a/source/reference/command/shardCollection.txt b/source/reference/command/shardCollection.txt
@@ -15,12 +15,17 @@ Definition
 
 .. dbcommand:: shardCollection
 
-   :doc:`Shards </sharding>` a collection to distribute its documents
-   across shards. You must run :dbcommand:`enableSharding` on a
-   database before running the :dbcommand:`shardCollection` command.
-   The :dbcommand:`shardCollection` command must be run against the
+   :doc:`Shards </sharding>` a collection to distribute its documents across
+   shards. The :dbcommand:`shardCollection` command must be run against the
    ``admin`` database.
 
+   .. note::
+
+      .. versionchanged:: 6.0
+
+      Starting in MongoDB 6.0, sharding a collection does **not** require you to
+      first run the :dbcommand:`enableSharding` command to configure the database.
+
    .. |command| replace:: :dbcommand:`shardCollection`
 
    .. include:: /includes/fact-dbcommand.rst
diff --git a/source/reference/method.txt b/source/reference/method.txt
@@ -976,7 +976,7 @@ Sharding
 
    * - :method:`sh.enableSharding()`
 
-     - Enables sharding on a specific database.
+     - Creates a database.
 
    * - :method:`sh.getBalancerHost()`
 
diff --git a/source/reference/method/js-sharding.txt b/source/reference/method/js-sharding.txt
diff --git a/source/reference/method/sh.enableSharding.txt b/source/reference/method/sh.enableSharding.txt
diff --git a/source/reference/method/sh.shardCollection.txt b/source/reference/method/sh.shardCollection.txt
diff --git a/source/reference/operator/aggregation/merge.txt b/source/reference/operator/aggregation/merge.txt
diff --git a/source/reference/sharding.txt b/source/reference/sharding.txt
diff --git a/source/tutorial/deploy-shard-cluster.txt b/source/tutorial/deploy-shard-cluster.txt
diff --git a/source/tutorial/deploy-sharded-cluster-with-keyfile-access-control.txt b/source/tutorial/deploy-sharded-cluster-with-keyfile-access-control.txt
