diff --git a/source/reference/command/replSetGetStatus.txt b/source/reference/command/replSetGetStatus.txt index 4ec726da66a..80d670c58b6 100644 --- a/source/reference/command/replSetGetStatus.txt +++ b/source/reference/command/replSetGetStatus.txt @@ -669,8 +669,6 @@ following fields: .. data:: replSetGetStatus.term - .. versionadded:: 3.2 - The election count for the replica set, as known to this replica set member. The :data:`~replSetGetStatus.term` is used by the distributed consensus algorithm to ensure correctness. @@ -683,8 +681,6 @@ following fields: .. data:: replSetGetStatus.syncSourceHost - .. versionadded:: 4.0, 3.6.6, 3.4.16 - The :data:`~replSetGetStatus.syncSourceHost` field holds the hostname of the member from which this instance syncs. @@ -694,8 +690,6 @@ following fields: .. data:: replSetGetStatus.syncSourceId - .. versionadded:: 4.0, 3.6.6, 3.4.16 - The :data:`~replSetGetStatus.syncSourceId` field holds the :data:`replSetGetStatus.members[n]._id` of the member from which this instance syncs. @@ -706,8 +700,6 @@ following fields: .. data:: replSetGetStatus.heartbeatIntervalMillis - .. versionadded:: 3.2 - The frequency in milliseconds of the heartbeats. .. data:: replSetGetStatus.majorityVoteCount @@ -744,8 +736,6 @@ following fields: .. data:: replSetGetStatus.optimes - .. versionadded:: 3.4 - The ``optimes`` field holds a document that contains :term:`optimes ` used to inspect replication progress. Starting in MongoDB 4.2, the ``optimes`` include the corresponding ISODate-formatted @@ -840,8 +830,6 @@ following fields: A ``null`` value indicates that no stable checkpoint exists. - .. versionadded:: 4.0 - .. data:: replSetGetStatus.lastStableRecoveryTimestamp .. versionadded:: 4.2 @@ -1045,7 +1033,6 @@ following fields: .. data:: replSetGetStatus.initialSyncStatus - .. versionadded:: 3.4 A document provides information on the progress and status of :ref:`initial sync ` on this member. @@ -1054,55 +1041,42 @@ following fields: .. data:: replSetGetStatus.initialSyncStatus.failedInitialSyncAttempts - .. versionadded:: 3.4 The number of times the :ref:`initial sync ` failed and had to restart on this member. - .. include:: /includes/fact-rs-status-init-sync-availability.rst .. data:: replSetGetStatus.initialSyncStatus.maxFailedInitialSyncAttempts - .. versionadded:: 3.4 The maximum number of times the :ref:`initial sync ` can restart on this member before the member shuts down. - .. include:: /includes/fact-rs-status-init-sync-availability.rst .. data:: replSetGetStatus.initialSyncStatus.initialSyncStart - .. versionadded:: 3.4 The start timestamp of the :ref:`initial sync ` for this member. - .. include:: /includes/fact-rs-status-init-sync-availability.rst .. data:: replSetGetStatus.initialSyncStatus.initialSyncEnd - .. versionadded:: 3.4 The end timestamp of the :ref:`initial sync ` for this member. - .. include:: /includes/fact-rs-status-init-sync-availability.rst - .. data:: replSetGetStatus.initialSyncStatus.initialSyncElapsedMillis - .. versionadded:: 3.4 - The number of milliseconds between :data:`~replSetGetStatus.initialSyncStatus.initialSyncStart` and :data:`~replSetGetStatus.initialSyncStatus.initialSyncEnd`. - .. include:: /includes/fact-rs-status-init-sync-availability.rst .. data:: replSetGetStatus.initialSyncStatus.initialSyncAttempts - .. versionadded:: 3.4 Array of documents where each document corresponds to a single :ref:`initial sync ` attempt. For example: @@ -1161,11 +1135,9 @@ following fields: See also :data:`~replSetGetStatus.initialSyncStatus.failedInitialSyncAttempts`. - .. include:: /includes/fact-rs-status-init-sync-availability.rst .. data:: replSetGetStatus.initialSyncStatus.appliedOps - .. versionadded:: 3.4 The number of ops that occurred after the :ref:`initial sync ` started and were applied after cloning @@ -1175,11 +1147,9 @@ following fields: to update its data set to reflect the current state of the replica set. - .. include:: /includes/fact-rs-status-init-sync-availability.rst .. data:: replSetGetStatus.initialSyncStatus.initialSyncOplogStart - .. versionadded:: 3.4 The start timestamp of the oplog application stage of the :ref:`initial sync ` where the @@ -1190,11 +1160,9 @@ following fields: to update its data set to reflect the current state of the replica set. - .. include:: /includes/fact-rs-status-init-sync-availability.rst .. data:: replSetGetStatus.initialSyncStatus.initialSyncOplogEnd - .. versionadded:: 3.4 The end timestamp of the oplog application stage of the :ref:`initial sync ` where the @@ -1205,7 +1173,6 @@ following fields: to update its data set to reflect the current state of the replica set. - .. include:: /includes/fact-rs-status-init-sync-availability.rst .. data:: replSetGetStatus.initialSyncStatus.syncSourceUnreachableSince @@ -1214,8 +1181,6 @@ following fields: Only present if the if sync source is unavailable during the current initial sync. - .. include:: /includes/fact-rs-status-init-sync-availability.rst - .. versionadded:: 4.4 .. data:: replSetGetStatus.initialSyncStatus.currentOutageDurationMillis @@ -1225,8 +1190,6 @@ following fields: Only present if the if sync source is unavailable during the current initial sync. - .. include:: /includes/fact-rs-status-init-sync-availability.rst - .. versionadded:: 4.4 .. data:: replSetGetStatus.initialSyncStatus.totalTimeUnreachableMillis @@ -1234,32 +1197,21 @@ following fields: The total time in milliseconds that the member has been unavailable during the current initial sync. - .. include:: /includes/fact-rs-status-init-sync-availability.rst - .. versionadded:: 4.4 .. data:: replSetGetStatus.initialSyncStatus.databases - .. versionadded:: 3.4 - Detail on the databases cloned during :ref:`initial sync `. - .. include:: /includes/fact-rs-status-init-sync-availability.rst - .. data:: replSetGetStatus.initialSyncStatus.databases.databasesCloned - .. versionadded:: 3.4 Number of databases cloned during :ref:`initial sync `. - .. include:: /includes/fact-rs-status-init-sync-availability.rst - .. data:: replSetGetStatus.initialSyncStatus.databases. - .. versionadded:: 3.4 - For each database, a document that returns information regarding the progress of the cloning of that database. @@ -1283,8 +1235,6 @@ following fields: } } - .. include:: /includes/fact-rs-status-init-sync-availability.rst - .. data:: replSetGetStatus.members @@ -1346,8 +1296,6 @@ following fields: Information regarding the last operation from the operation log that this member has applied. - .. versionchanged:: 3.2 - ``optime`` returns a document that contains: - ``ts``, the :ref:`Timestamp ` of @@ -1359,8 +1307,6 @@ following fields: .. data:: replSetGetStatus.members[n].optimeDurable - .. versionadded:: 3.4 - Information regarding the last operation from the operation log that this member has applied to its journal. @@ -1384,8 +1330,6 @@ following fields: .. data:: replSetGetStatus.members[n].optimeDurableDate - .. versionadded:: 3.4 - An :term:`ISODate` formatted date string that reflects the last entry from the :term:`oplog` that this member applied to its journal. @@ -1452,8 +1396,6 @@ following fields: .. data:: replSetGetStatus.members[n].syncSourceHost - .. versionadded:: 4.0, 3.6.6, 3.4.16 - The :data:`~replSetGetStatus.members[n].syncSourceHost` field holds the hostname of the member from which this instance syncs. @@ -1464,8 +1406,6 @@ following fields: .. data:: replSetGetStatus.members[n].syncSourceId - .. versionadded:: 4.0, 3.6.6, 3.4.16 - The :data:`~replSetGetStatus.members[n].syncSourceId` field holds the :data:`replSetGetStatus.members[n]._id` value of the :data:`~replSetGetStatus.members[n].syncSourceHost`.