DOCS-16392 Document periodicNoopIntervalSecs (#4975) (#5054)

* DOCS-16392 Document periodicNoopIntervalSecs

* IF feedback

Author: ajhuh-mdb

source/administration/change-streams-production-recommendations.txt

@@ -67,7 +67,9 @@ no activity for the collection, or are "cold", can negatively affect the
 response time of the change stream as the :binary:`~bin.mongos` must still check
 with those cold shards to guarantee total ordering of changes. This effect may
 be more apparent with geographically distributed shards, or workloads where
-the majority of operations occur on a subset of shards in the cluster.
+the majority of operations occur on a subset of shards in the cluster. To 
+minimize latency for cold shards, you can specify a lower
+:parameter:`periodicNoopIntervalSecs` value.
 
 If a sharded collection has high levels of activity, the :binary:`~bin.mongos`
 may not be able to keep up with the changes across all of the shards.

source/reference/parameters.txt

@@ -2116,6 +2116,31 @@ Logical Session
 
       mongod --setParameter maxSessions=1000
 
+.. parameter:: periodicNoopIntervalSecs
+
+   |mongod-only|
+
+   *Type*: integer
+
+   *Default*: 10
+
+   The duration in seconds between :term:`noop` writes on each individual node.
+
+   You can only set the parameter during startup, and cannot change
+   this setting using the :dbcommand:`setParameter` database command.
+
+   .. note:: 
+
+      To modify this value for a :atlas:`MongoDB Atlas </>` cluster, you
+      must contact :atlas:`Atlas Support </support>`.
+
+   The following example sets the ``periodicNoopIntervalSecs`` to 1 second at 
+   startup:
+
+   .. code-block:: javascript
+
+      mongod --setParameter periodicNoopIntervalSecs=1
+
 .. parameter:: TransactionRecordMinimumLifetimeMinutes
 
    .. versionadded:: 3.6