Skip to content

Commit 16935f9

Browse files
author
Ed Costello
committed
DOCS-741 add mem.mappedWithJournal to serverStatus
1 parent e59e2c7 commit 16935f9

File tree

1 file changed

+11
-2
lines changed

1 file changed

+11
-2
lines changed

source/reference/server-status.txt

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -410,7 +410,7 @@ mem
410410

411411
.. status:: mem.virtual
412412

413-
:status:`mem.virtual` displays the quantity, in bytes, of virtual memory
413+
:status:`mem.virtual` displays the quantity, in Mb, of virtual memory
414414
used by the :program:`mongod` process. In typical deployments this value
415415
is slightly larger than :status:`mem.mapped`. If this value is
416416
significantly (i.e. gigabytes) larger than :status:`mem.mapped`,
@@ -428,10 +428,19 @@ mem
428428

429429
.. status:: mem.mapped
430430

431-
The value of :status:`mem.mapped` provides the amount of mapped memory by
431+
The value of :status:`mem.mapped` provides the amount of mapped memory,
432+
in Mb, by
432433
the database. Because MongoDB uses memory-mapped files, this value
433434
is likely to be to be roughly equivalent to the total size of your
434435
database or databases.
436+
437+
.. status:: mem.mappedWithJournal
438+
439+
:status:`mem.mappedWithJournal` provides the amount of
440+
mapped memory, in Mb, including the memory used for
441+
journaling.
442+
This value will always be twice the value of :status:`mem.mapped`.
443+
This field is only included if journaling is enabled.
435444

436445
.. _server-status-connections:
437446

0 commit comments

Comments
 (0)