Skip to content

DOCS-11248: asserts.wranings = 0 #3291

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
Apr 13, 2018
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
8 changes: 6 additions & 2 deletions source/reference/command/serverStatus.txt
Original file line number Diff line number Diff line change
Expand Up @@ -160,8 +160,12 @@ asserts

.. serverstatus:: asserts.warning

The number of warnings raised since the MongoDB process started.
Check the log file for more information about these warnings.
.. versionchanged:: 4.0

Starting in MongoDB 4.0, the field returns zero ``0``.

In earlier versions, the field returns the number of warnings raised
since the MongoDB process started.

.. serverstatus:: asserts.msg

Expand Down
5 changes: 4 additions & 1 deletion source/release-notes/4.0-compatibility.txt
Original file line number Diff line number Diff line change
Expand Up @@ -84,9 +84,12 @@ uses master-slave replication, you must upgrade to a replica set.
To convert your master-slave replication, see
:ref:`convert-master-slave-to-replica-set`.

.. _4.0-compatibility-general:

General
-------

- Remove ``mongoperf``.


- The :dbcommand:`serverStatus` command now always returns ``0`` for
the :serverstatus:`asserts.warning` field.