[DOCS-6370] The explain of db.serverStatus on WiredtiGER Created: 14/Oct/15  Updated: 26/Jul/18  Resolved: 09/Jan/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: liyang zhou Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 6 years, 5 weeks, 2 days ago

 Description   

db.serverStatus().wiredTiger shows a log of things.
But I can not find any of this item in the document.

I have no idea which of them is useful,or what`s the meaning of them.
Like the return of db.serverStatus().wiredTiger.cache

{
        "tracked dirty bytes in the cache" : 25741348,
        "tracked bytes belonging to internal pages in the cache" : 55454176753,
        "bytes currently in the cache" : 3430851169,
        "tracked bytes belonging to leaf pages in the cache" : NumberLong("9223372036854775807"),
        "maximum bytes configured" : 4294967296,
        "tracked bytes belonging to overflow pages in the cache" : 0,
        "bytes read into cache" : NumberLong("1369313451711"),
        "bytes written from cache" : 703660481848,
        "pages evicted by application threads" : 82877,
        "checkpoint blocked page eviction" : 9039,
        "unmodified pages evicted" : 50377821,
        "page split during eviction deepened the tree" : 0,
        "modified pages evicted" : 22454998,
        "pages selected for eviction unable to be evicted" : 3316349,
        "pages evicted because they exceeded the in-memory maximum" : 17,
        "pages evicted because they had chains of deleted items" : 362314,
        "failed eviction of pages that exceeded the in-memory maximum" : 34109,
        "hazard pointer blocked page eviction" : 2772938,
        "internal pages evicted" : 2167450,
        "maximum page size at eviction" : 15481714,
        "eviction server candidate queue empty when topping up" : 483082,
        "eviction server candidate queue not empty when topping up" : 853628,
        "eviction server evicting pages" : 6195617,
        "eviction server populating queue, but not evicting pages" : 1000198,
        "eviction server unable to reach eviction goal" : 11,
        "pages split during eviction" : 266859,
        "pages walked for eviction" : 31445786857,
        "eviction worker thread evicting pages" : 69577117,
        "in-memory page splits" : 8,
        "percentage overhead" : 8,
        "tracked dirty pages in the cache" : 618,
        "pages currently held in the cache" : 116937,
        "pages read into cache" : 73221060,
        "pages written from cache" : 49983684
}                                                                          

or db.serverStatus().wiredTiger.cursor or something else

Hope for your return



 Comments   
Comment by Kay Kim (Inactive) [ 09/Jan/18 ]

Hi liyang –
thanks for filing this ticket. Currently, we only doc the ones that we felt were most significant on the page mentioned in the above comment. As such, will close the ticket as works as designed. If we have missed updates to the more significant items, we will of course add.

Comment by Daniel Coupal [ 08/Jan/18 ]

Liyang,

The most important metrics are described at:
https://docs.mongodb.com/manual/reference/command/serverStatus

Regards,
Daniel Coupal

Generated at Thu Feb 08 07:52:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.