@@ -994,13 +994,13 @@ Journaling
994
994
.. note::
995
995
996
996
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.
1004
1004
1005
1005
See the ":wiki:`Journaling`" wiki page for more information about
1006
1006
journaling operations.
@@ -1010,24 +1010,22 @@ Journaling
1010
1010
.. status:: dur.commits
1011
1011
1012
1012
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>`.
1015
1015
1016
1016
.. status:: dur.journaledMB
1017
1017
1018
1018
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>`.
1022
1022
1023
1023
.. status:: dur.writeToDataFilesMB
1024
1024
1025
1025
The :status:`dur.writeToDataFilesMB` provides the amount of data in
1026
1026
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
+
1031
1029
.. status:: dur.compression
1032
1030
1033
1031
.. versionadded:: 2.0
@@ -1048,26 +1046,26 @@ Journaling
1048
1046
1049
1047
.. status:: dur.earlyCommits
1050
1048
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.
1057
1055
1058
1056
.. status:: dur.timeMS
1059
1057
1060
1058
The :status:`dur.timeMS` document provides information about the
1061
1059
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>`.
1065
1062
1066
1063
.. status:: dur.timeMS.dt
1067
1064
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.
1071
1069
1072
1070
.. status:: dur.timeMS.prepLogBuffer
1073
1071
0 commit comments