[Mongodb]db.serverstatus () Order detailed

Basic Information

Spock:primary>db.serverstatus ()

{

"Host": "h6.corp.yongche.org",//Host name

"Version": "2.6.2",//mongodb version

"Process": "Mongod",//mongodb processes, mainly Mongod and MONGOs (fragmented cluster) two

"pid": Numberlong (4205),//mongod PID process number, available shell pidof mongod command validation

"Uptime": 173120, the number of seconds that the//mongod service has been alive since it started

"Uptimemillis": Numberlong (173119573),//mongod the number of milliseconds after service startup to now exist

"Uptimeestimate": 172173, the number of surviving seconds calculated inside//mongod

"LocalTime": Isodate ("2014-12-31t06:41:01.029z")/local time

Lock Information

MongoDB has 4 kinds of locks: r,r,w,w

R: Indicates a global read lock

W: Global Write lock

R: a database read lock

W: a Database write lock

Spock:primary>db.serverstatus (). Locks

{

"." : {

"Timelockedmicros": {

"R": Numberlong (2532219), total number of microseconds holding global read locks for all libraries after//mongod startup

"W": Numberlong (2022505)///Mongod total number of microseconds holding global write locks for all libraries after startup

},

"Timeacquiringmicros": {

"R": Numberlong (1489378),////Mongod total microseconds for lock waits for all library global read locks after startup

"W": Numberlong (361350)///Mongod total number of microseconds for lock waits for all library global write locks after startup

}

},

' Admin ': {

"Timelockedmicros": {

"R": Numberlong (277350),//Mongod read-lock time held by admin database after startup

"W": Numberlong (0)//Mongod write lock time held by admin database after startup

},

"Timeacquiringmicros": {

"R": Numberlong (11011),//Lock wait total time for read lock of admin database after Mongod started

"W": Numberlong (0)//mongod lock wait total time for read lock of admin database after startup

}

},

"Local": {

"Timelockedmicros": {

"R": Numberlong (29750564),

"W": Numberlong (737)

},

"Timeacquiringmicros": {

"R": Numberlong (4074456),

"W": Numberlong (46)

}

},

"Jiangjianjian": {

"Timelockedmicros": {

"R": Numberlong (935802), read-lock time held by//mongod Jiangjianjian database after startup

"W": Numberlong//Mongod after startup Jiangjianjian database hold write lock time

},

"Timeacquiringmicros": {

"R": Numberlong (262185),//Mongod lock wait total time for read lock on Jiangjianjian database after startup

"W": Numberlong (9)//Mongod Lock Wait total time of the Jiangjianjian database after startup

}

},

' Test ': {

"Timelockedmicros": {

"R": Numberlong (719696),

"W": Numberlong (141)

},

"Timeacquiringmicros": {

"R": Numberlong (332797),

"W": Numberlong (10)

}

}

}

Global Lock Information

Spock:primary>db.serverstatus (). GlobalLock

{

"TotalTime": Numberlong ("172059990000"),//mongod boot up to now total time, unit microseconds

"Locktime": Numberlong (2031058),//mongod total time of global lock lock after startup, unit microseconds

"Currentqueue": {

"Total": 0,//current global lock wait number of lock waits

"Readers": 0,//current global read lock wait number

"Writers": 0//Current global write lock wait number

},

"Activeclients": {

"Total": 0,//current number of active clients

"Readers": 0,//The number of read operations in the current active client

"Writers": 0//The number of write operations in the current active client

}

}

Memory Information

Bj1-farm1:primary>db.serverstatus (). Mem

{

"Bits": 64,//OS digits

"Resident": 45792,//physical memory consumption, Unit m

"Virtual": 326338,//fictitious memory consumption

' Supported ': TRUE,//TRUE indicates support for displaying additional memory information

"Mapped": 161399,//mapped memory

"Mappedwithjournal": 322798//In addition to mapped memory also includes journal log consumption of mapped memory

}

About MongoDB memory of the introduction can refer to my blog

http://blog.csdn.net/cug_jiang126com/article/details/42264895

Connection number Information

Bj1-farm1:primary>db.serverstatus (). connections

{

"Current": 2581,//number of connections

"Available": 48619,//number of available connections

"Totalcreated": Numberlong (187993238)//The total number of connections created so far

}

You can see that the maximum number of connections for the current Mongod is 51200=2581+48619

Additional Information

Bj1-farm1:primary>db.serverstatus (). Extra_info

{

"Note": "Fields vary byplatform",//indicates that the current display information for this extra_info relies on the underlying system

"Heap_usage_bytes": 206033064,//heap memory space occupied by the number of bytes, only Linux applicable

"Page_faults": 11718117//The number of pages when the database accesses data that is not in memory, and when the database performance is poor or the data is large, this value increases significantly

}

Index statistical Information

Bj1-farm1:primary>db.serverstatus (). indexcounters

{

"Accesses": 35369670951,//Index access times, the greater the value of your index is generally built better, if the value of slow growth, indicating that the system built index is problematic

"Hits": 35369213426,//index hit times, larger value indicates mogond better use of index

"Misses": 0,//indicates the number of times the mongod is not in memory when trying to use the index, the smaller the better

"Resets": 0,//counter reset number of times

"Missratio": 0//loss rate, i.e. misses divided by hits value

}

Background Refresh Information

Bj1-farm1:primary>db.serverstatus (). backgroundflushing

{

"Flushes": 171675,//Database refresh write to disk total number of times, will gradually increase

"Total_ms": 432943335,//mongod write data to disk consumption total time, unit MS,

"Average_ms": 2521.8775884665793,//The ratio of the above two values, representing the average time of each disk write

"Last_ms": 5329,//Current last write Disk Time spent, MS, combined with the last average can be observed mongd overall write performance and current write performance

"Last_finished": Isodate ("2014-12-31t07:39:11.881z")//time of last write completion

}

Cursor Information

Bj1-farm1:primary>db.serverstatus (). Cursors

{

"Note": "Deprecated,use Server Status Metrics",//indicates that b.serverstatus () can also be used. Metrics.cursor command to see

"Clientcursors_size": 2,//mongodb the number of cursors currently maintained for the client

"Totalopen": 2,//Same as Clientcursors_size

"pinned": 0,//open pinned type of cursor number

"Totalnotimeout": 0,//Set the number of cursors opened after a period of inactivity, that is, when the parameter "DBQuery.Option.noTimeout" value is not set

"TimedOut": Number of cursor timeouts since Mongod started, if this value is large or has been growing, it may show that the current application has an error

}

Network Information

Bj1-farm1:primary>db.serverstatus (). Network

{

"Bytesin": Numberlong ("1391919214603"),//The number of network bytes transmitted by the database, which can be observed to see if the expected expectation

"Bytesout": Numberlong ("1669479449423"),//number of bytes transmitted from the database

"Numrequests": Total number of requests received by 5186060375//mongod

}

Replica Set Information

Bj1-farm1:primary>db.serverstatus (). repl

{

"SetName": "Bj1-farm1",//Replica set name

"Setversion": 4,//current version, per modified configuration will be increased by 1

' IsMaster ': true,//whether the current node is master

' Secondary ': false,//current node is slave

"Hosts": [//Replica set composition

"172.16.0.150:27017",

"172.16.0.152:27017",

"172.16.0.151:27017"

],

"PRIMARY": "172.16.0.150:27017",//master IP Address

"Me": "172.16.0.150:27017"//IP address of the current node

}

About more copy set management and introduction see my Blog

http://blog.csdn.net/cug_jiang126com/article/details/41943237

operation counters for replica sets

Bj1-farm1:primary>db.serverstatus (). Opcountersrepl

{

Insert: 599,//Mongod replication Insert count after last boot

"Query": 0,

"Update": 0,

"Delete": 0,

"Getmore": 0,

"Command": 0

}

Action Counter

Bj1-farm1:primary>db.serverstatus (). opcounters

{

Insert: 17476744,//mongod the number of inserts since the last boot

"Query": 4923585,//Mongod query times after the most recent startup

"Update": 445136,//mongod update number after last boot

' Delete ': 301953,//mongod number of deletes after last startup

"Getmore": 28737548,//mongod number of Getmore after the most recent boot, this value can be high because the child node sends the Getmore command as part of the data copy operation

Command: 32844821////mongod The number of command commands executed after the most recent startup

}

Asserts

Bj1-farm1:primary>db.serverstatus (). Asserts

{

"Regular": 65,//service after the start of the normal number of asserts errors, you can view more this information through the log

"Warning": 1,//The number of warning after service startup

"MSG": 0,//The number of message asserts after service startup

"User": 30655213,//number of user asserts after service startup

"rollovers": 0//reset times after service startup

} writebacksqueued

Bj1-farm1:primary>db.serverstatus (). writebacksqueued

False//If TRUE indicates that there is an action that needs to be performed again if False indicates no

persistence (dur)

Bj1-farm1:primary>db.serverstatus (). Dur

{

"Commits": 29,///number of commits written to Journal after the last group commit interval

"JOURNALEDMB": 1.089536,///after the last packet submission interval, write the size of the journal, Unit m

"WRITETODATAFILESMB": 2.035345,///the size of the data file written from journal after the last group commit interval

"Compression": Compression rate of 0.49237888647866956,//journal log

"Commitsinwritelock": 0,//the number of times to write a lock, you can use this value to determine the current system write pressure

"Earlycommits": 0,//The number of requests for a commit before the packet submission interval. This value is used to determine the packet submission interval, that is, whether the journal group Commitinterval is set reasonably

"Timems": {

"DT": 3060,//time spent collecting data, Unit ms

"Preplogbuffer": 7,//ready to write journal time spent, unit MS, the smaller the value indicates the better the journal Performance

"Writetojournal": 36,////The time spent in the actual write journal, unit MS, this value is related to the file system and hardware Device

"Writetodatafiles": 34,//time spent writing from journal to data file, Unit ms

"Remapprivateview": 18//Remapping the time spent in memory, unit MS, the smaller the value indicates the better the journal Performance

}

}

If the group commit interval is set, the entry also displays the Journalcommitintervalms information, the commit interval, the default 100ms.

Record status information

Bj1-farm1:primary>db.serverstatus (). recordstats

{

"Accessesnotinmemory": 4444249,//The total number of times when accessing data that is not in memory

"Pagefaultexceptionsthrown": 22198,//Total number of exceptions thrown due to page faults

"Yc_driver": {

"Accessesnotinmemory": 53441,

"Pagefaultexceptionsthrown": 18067

},

"Yc_foot_print": {

"Accessesnotinmemory": 0,

"Pagefaultexceptionsthrown": 0

}

Working Set Configuration

Bj1-farm1:primary>db.serverstatus ({workingset:1}). workingset

{

"Note": "Thisisanestimate",//Notes

"Pagesinmemory": 736105, the number of pages in memory//overseconds time, the default page size 4k; If your dataset is smaller than memory, the value is converted to size, which is the size of the dataset; You can use this value to estimate the size of the actual working set

"Computationtimemicros": 232590,//The time spent collecting working set data, in microseconds, collecting this information will affect server performance, please note the frequency of collection working set

"Overseconds": 502//Memory time, in seconds, between the latest data and the oldest data page. If the value is decreasing, or the value is small, the working set is already much larger than the memory value, and if the value is large, it represents the data set <= memory value

}

Metrics

Bj1-farm1:primary>db.serverstatus (). Metrics

{

"Cursor": {//cursor information has been described above

"TimedOut": Numberlong (12),

' Open ': {

"Notimeout": Numberlong (0),

"Pinned": Numberlong (0),

"Total": Numberlong (2)

}

},

"Document": {

"Deleted": Numberlong (4944851),//delete total number of records

"Inserted": Numberlong (1066509660),//Insert total number of records

"Returned": Numberlong ("4594388182"),//Returns the total number of records

"Updated": Numberlong (27275088)//update total number of records

},

"GetLastError": {

"Wtime": {

"num": 0,//w>1 number of GetLastError

"Totalmillis": 0//Time

},

"Wtimeouts": Numberlong (0)//timeout number

},

This section refers to the official document in detail

http://docs.mongodb.org/manual/reference/command/getLastError/#dbcmd. GetLastError

http://docs.mongodb.org/manual/reference/command/serverStatus/#metrics

"Operation": {

"Fastmod": Numberlong (23990485),//using $INC operation to increase data logging, and the column does not use the index update number

"Idhack": Numberlong (0),//number of queries using the _id column, this is MongoDB will default to use _ID index and skip query plan resolution

"Scanandorder": Numberlong (33042)//number of times the index cannot be sorted using

},

"Queryexecutor": {

"Scanned": Numberlong ("334236661328319"),//Total number of rows scanned in the query or query plan

"Scannedobjects": Numberlong ("776725143947")//

},

' Record ': {

"Moves": Numberlong (44166)//The total number of times the document was moved on the hard disk

},

"Repl": {

"Apply": {

"Batches": {

"num": 162,//Oplog number of application processes for slave nodes in the replica set

"Totalmillis": Total time taken by//mongod to operate from Oplog

},

"OPS": Total number of Numberlong (599)//oplog operations

},

"Buffer": {

"Count": Numberlong (0), number of current operations in//oplog buffer

"Maxsizebytes": 268435456, maximum value of//oplog buffer, constant, no longer configurable

"Sizebytes": Numberlong (0)//current Oplog buffer size

},

"Network": {

"bytes": Numberlong (282864),//Total amount of data read from the copy source

"Getmores": {

"num": 164,//number of getmores operations performed

"Totalmillis": Total time spent 15595//getmores operation

},

"Ops": Numberlong (599),//Total number of operations read from the replication source

"Readerscreated": Numberlong (a)//oplog query thread creation number, when sending connection,timeout, or network operation, select the copy source again, this value will increase

},

"Preload": {

"Docs": {

"num": 0,

"Totalmillis": 0

},

"Indexes": {

"num": 2396,

"Totalmillis": 0

}

}

},

"Storage": {

"Freelist": {

"Search": {

"Bucketexhausted": Numberlong (0),

"Requests": Numberlong (1091000085),

"Scanned": Numberlong (1139483866)

}

}

},

"TTL": {

"Deleteddocuments": Numberlong (1015082231),//The Number of times the TTL index was used

"Passes": Numberlong (174032)//The number of times the document was deleted using the TTL index

}

}