Skip to content

DOCS-415 diaglogging: add warning that log is kept open by mongod #280

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 4, 2012
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions source/administration/configuration.txt
Original file line number Diff line number Diff line change
Expand Up @@ -342,7 +342,7 @@ needed:
Each additional level ``v`` adds additional verbosity to the
logging. The ``verbose`` option is equal to ``v = true``.

- :setting:`diaglog` enables diagnostic logging. Level ``3``
- :setting:`diaglog` enables :term:`diagnostic logging <diagnostic log>`. Level ``3``
logs all read and write options.

- :setting:`objcheck` forces :program:`mongod` to validate all
Expand All @@ -352,7 +352,7 @@ needed:
performance.

- :setting:`cpu` forces :program:`mongod` to report the percentage of
the last interval spent in :term:`write-lock`. The interval is
typically 4 seconds, and each output line in the log includes both
the actual interval since the last report and the percentage of
time spent in write lock.
the last interval spent in :term:`write-lock`. The interval is
typically 4 seconds, and each output line in the log includes both
the actual interval since the last report and the percentage of
time spent in write lock.
8 changes: 8 additions & 0 deletions source/includes/warning-diaglogging-off.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@

.. warning::

Setting the diagnostic level to ``0`` will cause :program:`mongod`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • s/will cause/causes/
  • blank line at the beginning of the file. Intentional?

to stop writing data to the :term:`diagnostic log` file, however the
:program:`mongod` instance will continue to keep the file open.
If you want to rename, move, or delete the diagnostic log you must
cleanly shut down the :program:`mongod` instance before doing so.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don't have good documentation of what "clean shutdown" is.

9 changes: 6 additions & 3 deletions source/reference/configuration-options.txt
Original file line number Diff line number Diff line change
Expand Up @@ -269,10 +269,11 @@ Settings

*Default:* 0

Creates a very verbose, diagnostic log for troubleshooting and
Creates a very verbose, :term:`diagnostic log` for troubleshooting and
recording various errors. MongoDB writes these log files in the
:setting:`dbpath` in a series of files that begin with the string
``diaglog``.
:setting:`dbpath` directory in a series of files that begin with the string
``diaglog`` with the time logging was initiated appended as a hex
string.

The value of this setting configures the level of
verbosity. Possible values, and their impact are as follows.
Expand All @@ -298,6 +299,8 @@ Settings

:setting:`diaglog` is for internal use and not intended for most
users.

.. include:: /includes/warning-diaglogging-off.rst

.. setting:: directoryperdb

Expand Down
13 changes: 13 additions & 0 deletions source/reference/glossary.txt
Original file line number Diff line number Diff line change
Expand Up @@ -866,3 +866,16 @@ Glossary
results. The optimizer then uses the query plan each time the
query is run. If a collection changes significantly, the optimizer
creates a new query plan.

diagnostic log
:program:`mongod` can create a verbose log of operations with
the :option:`mongod --diaglog` option or through the
:dbcommand:`diagLogging` command. This log will be created in
the directory specified with the :option:`mongod --dbpath` option
or the default :file:`/data/db` directory. The log file will
be named :file:`diaglog.{time in hex}`, with the time when
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

angle brackets rather than curly brackets.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sphinx processes the {} in a :file: directive to italicize the enclosed text, it will appear as diaglog.time in hex in the resulting doc

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's a docutils thing. I changed it but we can change it back. shrug

On Friday, October 05 2012, 09:57:46, Ed Costello wrote:

@@ -866,3 +866,16 @@ Glossary
results. The optimizer then uses the query plan each time the
query is run. If a collection changes significantly, the optimizer
creates a new query plan.

  • diagnostic log
  •  :program:`mongod` can create a verbose log of operations with
    
  •  the :option:`mongod --diaglog` option or through the
    
  •  :dbcommand:`diagLogging` command.  This log will be created in
    
  •  the directory specified with the :option:`mongod --dbpath` option
    
  •  or the default :file:`/data/db` directory.  The log file will
    
  •  be named :file:`diaglog.{time in hex}`, with the time when
    

Sphinx processes the {} in a :file: directive to italicize the enclosed text, it will appear as diaglog.time in hex in the resulting doc


Reply to this email directly or view it on GitHub:
https://github.com/mongodb/docs/pull/280/files#r1773237

Sam Kleinman (@tychoish)
Lead Technical Writer
10gen (the MongoDB Company)
[email protected]

logging was initiated appended as a hexadecimal string.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fix passive verbs in this section.


.. include:: /includes/warning-diaglogging-off.rst

.. seealso:: :option:`mongod --diaglog`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • also :setting:diaglog

9 changes: 6 additions & 3 deletions source/reference/mongod.txt
Original file line number Diff line number Diff line change
Expand Up @@ -189,10 +189,11 @@ Options

.. option:: --diaglog <value>

Creates a very verbose, diagnostic log for troubleshooting and
Creates a very verbose, :term:`diagnostic log` for troubleshooting and
recording various errors. MongoDB writes these log files in the
:setting:`dbpath` in a series of files that begin with the string
``diaglog``.
:setting:`dbpath` directory in a series of files that begin with the string
``diaglog`` with the time logging was initiated appended as a hex
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

passive verb

string.

The specified value configures the level of verbosity. Possible
values, and their impact are as follows.
Expand All @@ -219,6 +220,8 @@ Options
:option:`--diaglog` is for internal use and not intended for most
users.

.. include:: /includes/warning-diaglogging-off.rst

.. option:: --directoryperdb

Alters the storage pattern of the data directory to store each
Expand Down