DOCS-11960: 4.2 remove repairDatabase

Author: kay-kim

config/redirects

@@ -1413,7 +1413,9 @@ raw: /master/release-notes/3.0-general-improvements -> ${base}/release-notes/3.0
 [v4.2-*]: /${version}/reference/method/db.collection.group -> ${base}/${version}/release-notes/4.2
 [v4.2-*]: /${version}/reference/operator/meta/maxScan -> ${base}/${version}/release-notes/4.2-compatibility/#remove-maxscan
 [v4.2-*]: /${version}/reference/method/cursor.maxScan -> ${base}/${version}/release-notes/4.2-compatibility/#remove-maxscan
-[v4.2-*]: /${version}//reference/command/geoNear -> ${base}/${version}/release-notes/4.2-compatibility/#remove-support-for-the-geonear-command
+[v4.2-*]: /${version}/reference/command/geoNear -> ${base}/${version}/release-notes/4.2-compatibility/#remove-support-for-the-geonear-command
+[v4.2-*]: /${version}/reference/command/repairDatabase -> ${base}/${version}/release-notes/4.2
+[v4.2-*]: /${version}/reference/method/db.collection.repairDatabase -> ${base}/${version}/release-notes/4.2
 
 
 # Redirects for 4.0 or earlier (i.e. before 4.2)

source/core/data-model-operations.txt

@@ -158,12 +158,7 @@ the following behaviors:
   size. The namespace file defaults to 16 MB.
 
   To change the size of the *new* namespace file, start the server with
-  the option :option:`--nssize \<new size MB\> <mongod --nssize>`. For
-  existing databases, after starting up the server with
-  :option:`--nssize <mongod --nssize>`, run the :method:`db.repairDatabase()` command
-  from the :binary:`~bin.mongo` shell. For impacts and considerations on
-  running :method:`db.repairDatabase()`, see
-  :dbcommand:`repairDatabase`.
+  the option :option:`--nssize \<new size MB\> <mongod --nssize>`.
 
 .. _faq-developers-embed-documents:
 

source/core/index-creation.txt

@@ -71,7 +71,7 @@ usable once the index build is complete.
 
    If MongoDB is building an index in the background, you cannot
    perform other administrative operations involving that collection,
-   including running :dbcommand:`repairDatabase`, dropping the
+   including dropping the
    collection (i.e. :method:`db.collection.drop()`), and running
    :dbcommand:`compact`. These operations will return an error during
    background index builds.

source/faq/concurrency.txt

@@ -276,8 +276,6 @@ lock at the database level for extended periods:
        :method:`db.collection.createIndexes()` issued *without*
        ``background`` set to ``true``
 
-   * - :dbcommand:`repairDatabase`
-     - :method:`db.repairDatabase()`
 
 
 The following administrative operations lock the database but only hold
@@ -329,9 +327,6 @@ The following MongoDB operations take a global exclusive lock:
 - :method:`db.copyDatabase()` obtains a :serverstatus:`global exclusive
   (W) lock <locks>` and will block other operations until it finishes.
 
-- :method:`db.repairDatabase()` obtains a :serverstatus:`global
-  exclusive (W) lock <locks>` and will block other operations until it
-  finishes.
 
 - Starting in MongoDB 4.0, :method:`db.collection.reIndex()` takes a
   :serverstatus:`global exclusive (W) lock <locks>` and will block

source/faq/replica-sets.txt

@@ -57,8 +57,6 @@ Why use journaling if replication already provides data redundancy?
 -------------------------------------------------------------------
 
 :term:`Journaling <journal>` facilitates faster crash recovery.
-Prior to journaling, crashes often required :dbcommand:`database repairs <repairDatabase>`
-or full data resync. Both were slow, and the first was unreliable.
 
 Journaling is particularly useful for protection
 against power failures, especially if your replica set resides in a single data

source/includes/apiargs-dbcommand-repairDatabase-field.yaml

@@ -8,15 +8,14 @@ would create the index but not index such documents.
 .. index-field-limit-reIndex
 
 Reindexing operations will error if the index entry for an indexed
-field exceeds the |limit|. Reindexing operations occur as part of
-:dbcommand:`compact` and :dbcommand:`repairDatabase` commands as well
+field exceeds the |limit|. Reindexing operations occur as part of the
+:dbcommand:`compact` command as well
 as the :method:`db.collection.reIndex()` method.
 
 Because these operations drop *all* the indexes from a collection and
 then recreate them sequentially, the error from the |limit| prevents
 these operations from rebuilding any remaining indexes for the
-collection and, in the case of the :dbcommand:`repairDatabase` command,
-from continuing with the remainder of the process.
+collection.
 
 .. index-field-limit-insert
 

source/includes/fact-index-key-length-operation-behaviors.rst

@@ -1,5 +1,5 @@
 If you are running with :term:`journaling <journal>` enabled, there is
-almost never any need to run :dbcommand:`repairDatabase` unless you
+almost never any need to run repair unless you
 need to recover from a disk-level data corruption. In the event of an
 unclean shutdown, the server will be able to restore the data files to
 a clean state automatically.

source/includes/note-repair.rst

@@ -737,9 +737,7 @@ name: repair
 args: null
 directive: option
 description: |
-  Runs a repair routine on all databases. This is equivalent
-  to shutting down and running the :dbcommand:`repairDatabase` database
-  command on all databases.
+  Runs a repair routine on all databases.
 
   .. include:: /includes/warning-repair.rst
 

source/includes/options-mongod.yaml

@@ -102,10 +102,6 @@ name: ":dbcommand:`repairCursor`"
 file: /reference/command/repairCursor
 description: "Returns a cursor that iterates over all valid documents in a collection."
 ---
-name: ":dbcommand:`repairDatabase`"
-file: /reference/command/repairDatabase
-description: "Rebuilds the database and indexes by discarding invalid or corrupt data."
----
 name: ":dbcommand:`setFeatureCompatibilityVersion`"
 file: /reference/command/setFeatureCompatibilityVersion
 description: "Enables or disables features that persist data that are backwards-incompatible."

source/includes/ref-toc-command-administration.yaml

@@ -142,10 +142,6 @@ name: ":method:`db.printSlaveReplicationInfo()`"
 file: /reference/method/db.printSlaveReplicationInfo
 description: "Prints a report of the status of the replica set from the perspective of the secondaries."
 ---
-name: ":method:`db.repairDatabase()`"
-file: /reference/method/db.repairDatabase
-description: "Runs a repair routine on the current database."
----
 name: ":method:`db.resetError()`"
 file: /reference/method/db.resetError
 description: "Resets the error message returned by :method:`db.getPrevError()` and :dbcommand:`getPrevError`."

source/includes/ref-toc-method-database.yaml

@@ -1,19 +1,14 @@
 .. warning::
 
-   - Before using :dbcommand:`repairDatabase`, make a backup copy of
-     the dbpath directory.
-
-   - Avoid running :dbcommand:`repairDatabase` against a replica set.
-     If you are trying to repair a :term:`replica set` member, and you
+   - If you are trying to repair a :term:`replica set` member, and you
      have access to an intact copy of your data (e.g. a recent backup
      or an intact member of the :term:`replica set`), you should
      restore from that intact copy (see
-     :doc:`/tutorial/resync-replica-set-member`), and **not** use
-     :dbcommand:`repairDatabase`.
+     :doc:`/tutorial/resync-replica-set-member`).
+
+   - Only use :option:`mongod --repair` if you have no other options.
 
-   - Only use the :dbcommand:`repairDatabase` command and associated
-     wrappers, including :method:`db.repairDatabase()` and
-     :option:`mongod --repair`, if you have no other options. These
-     operations remove and do not save any corrupt data during the
+   - Make a backup copy of the dbpath directory before running repair.
+     The operation removes without saving any corrupt data during the
      repair process.
 

source/includes/warning-repair.rst

@@ -140,7 +140,6 @@ Every database includes the following database administration roles:
    - :authaction:`enableProfiler`
    - :authaction:`reIndex`
    - :authaction:`renameCollectionSameDB`
-   - :authaction:`repairDatabase`
    - :authaction:`storageDetails`
    - :authaction:`validate`
 
@@ -432,7 +431,6 @@ Cluster Administration Roles
    Provides the following actions on *all* databases in the cluster:
 
    - :authaction:`killCursors`
-   - :authaction:`repairDatabase`
 
 .. _backup-and-restore-roles: