Skip to content

Commit c4a5d57

Browse files
committed
DOCS-436 serverStatus dur documentation
1 parent 1e677be commit c4a5d57

File tree

2 files changed

+29
-31
lines changed

2 files changed

+29
-31
lines changed

source/reference/server-status-index.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -306,9 +306,9 @@ The ":ref:`server-status-writebacksqueued`" document reports the number of
306306
.. _server-status-example-journaling:
307307

308308
The ":ref:`server-status-journaling`" document reports on data that
309-
reflect this :program:`mongod`'s journaling-related operations and
310-
performance during a `journal group commit interval
311-
<http://www.mongodb.org/display/DOCS/Journaling#Journaling-GroupCommits>`_:
309+
reflect this :program:`mongod` instance's journaling-related operations
310+
and performance during a :wiki:`journal group commit interval
311+
<Journaling#Journaling-GroupCommits>`:
312312

313313
.. code-block:: javascript
314314

source/reference/server-status.txt

Lines changed: 26 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -994,13 +994,13 @@ Journaling
994994
.. note::
995995

996996
The data values are **not** cumulative but are reset on a regular
997-
basis as determined by the `journal group commit interval
998-
<http://www.mongodb.org/display/DOCS/Journaling#Journaling-GroupCommits>`_.
999-
This interval is ~100 milliseconds (ms) by default (or 30ms if the
1000-
journal file is on the same file system as your data files) and
1001-
is cut by 1/3 when there is a :dbcommand:`getLastError` command
1002-
pending. The interval is configurable using the
1003-
``--journalCommitInterval`` option.
997+
basis as determined by the :wiki:`journal group commit interval
998+
<Journaling#Journaling-GroupCommits>`. This interval is ~100
999+
milliseconds (ms) by default (or 30ms if the journal file is on
1000+
the same file system as your data files) and is cut by 1/3 when
1001+
there is a :dbcommand:`getLastError` command pending. The
1002+
interval is configurable using the ``--journalCommitInterval``
1003+
option.
10041004

10051005
See the ":wiki:`Journaling`" wiki page for more information about
10061006
journaling operations.
@@ -1010,24 +1010,22 @@ Journaling
10101010
.. status:: dur.commits
10111011

10121012
The :status:`dur.commits` provides the number of transactions
1013-
written to :term:`journal` during the last `journal group commit
1014-
interval <http://www.mongodb.org/display/DOCS/Journaling#Journaling-GroupCommits>`_.
1013+
written to :term:`journal` during the last :wiki:`journal group
1014+
commit interval <Journaling#Journaling-GroupCommits>`.
10151015

10161016
.. status:: dur.journaledMB
10171017

10181018
The :status:`dur.journaledMB` provides the amount of data in
1019-
megabytes (MB) written to :term:`journal` during the last `journal group
1020-
commit interval
1021-
<http://www.mongodb.org/display/DOCS/Journaling#Journaling-GroupCommits>`_.
1019+
megabytes (MB) written to :term:`journal` during the last
1020+
:wiki:`journal group commit interval
1021+
<Journaling#Journaling-GroupCommits>`.
10221022

10231023
.. status:: dur.writeToDataFilesMB
10241024

10251025
The :status:`dur.writeToDataFilesMB` provides the amount of data in
10261026
megabytes (MB) written from :term:`journal` to the data files during the
1027-
last `journal group
1028-
commit interval
1029-
<http://www.mongodb.org/display/DOCS/Journaling#Journaling-GroupCommits>`_.
1030-
1027+
last :wiki:`journal group commit interval <Journaling#Journaling-GroupCommits>`.
1028+
10311029
.. status:: dur.compression
10321030

10331031
.. versionadded:: 2.0
@@ -1048,26 +1046,26 @@ Journaling
10481046

10491047
.. status:: dur.earlyCommits
10501048

1051-
The :status:`dur.earlyCommits` value reflects the number of time MongoDB
1052-
requested a commit before the scheduled `journal group commit
1053-
interval <http://www.mongodb.org/display/DOCS/Journaling#Journaling-GroupCommits>`_.
1054-
Use this value to ensure that your `journal group commit interval
1055-
<http://www.mongodb.org/display/DOCS/Journaling#Journaling-GroupCommits>`_
1056-
is not too long for your deployment.
1049+
The :status:`dur.earlyCommits` value reflects the number of time
1050+
MongoDB requested a commit before the scheduled :wiki:`journal group
1051+
commit interval <Journaling#Journaling-GroupCommits>`. Use this
1052+
value to ensure that your :wiki:`journal group commit interval
1053+
<Journaling#Journaling-GroupCommits>` is not too long for your
1054+
deployment.
10571055

10581056
.. status:: dur.timeMS
10591057

10601058
The :status:`dur.timeMS` document provides information about the
10611059
performance of the :program:`mongod` instance during the various
1062-
phases of journaling in the last `journal group commit
1063-
interval
1064-
<http://www.mongodb.org/display/DOCS/Journaling#Journaling-GroupCommits>`_.
1060+
phases of journaling in the last :wiki:`journal group commit
1061+
interval <Journaling#Journaling-GroupCommits>`.
10651062

10661063
.. status:: dur.timeMS.dt
10671064

1068-
The :status:`dur.timeMS.dt` value provides, in milliseconds, the amount
1069-
of time over which MongoDB collected the :status:`dur.timeMS` data. Use
1070-
this field to provide context to the other dur.timeMS field values.
1065+
The :status:`dur.timeMS.dt` value provides, in milliseconds, the
1066+
amount of time over which MongoDB collected the :status:`dur.timeMS`
1067+
data. Use this field to provide context to the other
1068+
:status:`dur.timeMS` field values.
10711069

10721070
.. status:: dur.timeMS.prepLogBuffer
10731071

0 commit comments

Comments
 (0)