DOCS-11801: repl rollback timelimit = 1 day

Author: kay-kim

source/core/replica-set-rollbacks.txt

@@ -117,16 +117,17 @@ In previous versions, a :binary:`~bin.mongod` instance will not
 roll back more than 300 megabytes of data and requires manual
 intervention if more than 300 megabytes of data need to be rolled back.
 
-
 Time Elapsed Limitations
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. versionchanged:: 4.0
 
-Starting in version 4.0, the server parameter
-:parameter:`rollbackTimeLimitSecs` allows the setting of the maximum
-time allowed from the common point to the last point in the oplog of the
-replica set member that is indicated for rollback.
+Starting in version 4.0, the rollback time limit defaults to 24 hours
+and is configurable using the parameter
+:parameter:`rollbackTimeLimitSecs`. :parameter:`rollbackTimeLimitSecs`
+allows the setting of the maximum time allowed from the common point to
+the last point in the oplog of the replica set member that is indicated
+for rollback.
 
 In previous versions, the rollback time limit is not configurable and is
 set to 30 minutes.

source/reference/parameters.txt

@@ -1308,7 +1308,7 @@ Replication Parameters
 
    *Type*: 64-bit integer
 
-   *Default*: 1800
+   *Default*: 86400  (1 day)
 
    Maximum age of data that will be rolled back in the event of a
    replication operations failure. If the time between the end of the

source/release-notes/4.0-compatibility.txt

@@ -121,6 +121,11 @@ a :binary:`~bin.mongod` instance will not roll back more than 300
 megabytes of data and requires manual intervention if more than 300
 megabytes of data need to be rolled back.
 
+Starting in MongoDB 4.0, the rollback time limit defaults to 1 day and
+is configurable using the new parameter
+:parameter:`rollbackTimeLimitSecs`. In earlier versions, the rollback
+time limit is not configurable and is set to 30 minutes.
+
 Sharded Clusters
 ----------------
 

source/release-notes/4.0.txt

@@ -513,9 +513,10 @@ Journaling and Replica Sets
 ``rollbackTimeLimitSecs`` Parameter Available
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-In MongoDB 4.0, a new :parameter:`rollbackTimeLimitSecs` parameter allows
-for the setting of the time limit in seconds between the common point
-and the last oplog write entry in a stepped-down primary.
+Starting in MongoDB 4.0, a new :parameter:`rollbackTimeLimitSecs`
+parameter allows for the setting of the time limit in seconds between
+the common point and the last oplog write entry for the member
+indicated for rollback. The default rollback time limit is 1 day.
 
 Wait for Background Index Builds
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -634,7 +635,7 @@ Resume Token Data Type Change
        For the corresponding MongoDB driver method, refer to your
        driver documentation.
 
-       .. versionadded:: 4.0 
+       .. versionadded:: 4.0
 
 .. _4.0-free-monitoring:
 
@@ -720,20 +721,20 @@ Platform Support
 - MongoDB 4.0 (Community & Enterprise) adds support for:
 
   - :doc:`Amazon Linux 2 </tutorial/install-mongodb-on-amazon>`
- 
+
   - :doc:`Debian 9 "Stretch" </tutorial/install-mongodb-on-debian>`
 
 - MongoDB 4.0 (Community) adds support for:
 
   - s390x RHEL 6.x
 
 - MongoDB 4.0 does not support SLES 11.
-  
+
   - Support for SLES 11 has also been removed in MongoDB 3.2.20+,
     3.4.15+, and 3.6.4+.
 
 - MongoDB 4.0 does not support Ubuntu 12.04.
-  
+
   - Support for Ubuntu 12.04 has also been removed in MongoDB 3.2.20+,
     3.4.15+, and 3.6.4+.
 
@@ -763,14 +764,14 @@ Commands
 - The command :dbcommand:`listCollections` takes Intent Shared lock on
   the database. In previous versions, the command takes Shared lock on
   the database.
- 
+
 - The command :dbcommand:`listCollections` and its :binary:`~bin.mongo`
   shell helper :method:`db.getCollectionInfos()` accepts the following
   option:
 
   - ``nameOnly`` to return only the collection names and types (which
     does not require collection locks).
-    
+
   - ``authorizedCollections`` to allow users without the required
     privilege to run :dbcommand:`listCollections` can run the command,
     with ``nameOnly: true, authorizedCollections: true``, to return the
@@ -797,9 +798,9 @@ Commands
 
   - ``uuids`` field that contains the collections and their
     corresponding UUIDs.
- 
+
 - The command :dbcommand:`killOp` now supports termination of queries that are
-  running on a :binary:`~bin.mongos`. When run on the ``mongos``, :dbcommand:`killOp` 
+  running on a :binary:`~bin.mongos`. When run on the ``mongos``, :dbcommand:`killOp`
   can kill queries that are running in more than one shard.
 
 Geospatial Query Improvements