设为首页 收藏本站
查看: 741|回复: 0

[经验分享] Mongodb {serverStatus:1} 详细解释

[复制链接]

尚未签到

发表于 2015-7-8 09:53:22 | 显示全部楼层 |阅读模式
> db.serverStatus()



FieldExample ValueExplanation

host
my.node.com
The hostname of this server


version
1.8.0-rc1-pre-
The version number of this server


process
mongod
What is the process? (mongod, mongos)


uptime
14143
Uptime in seconds


uptimeEstimate
12710
Uptime based on MongoDB's internal coarse grained timer


localTime
ISODate("2011-03-01T05:30:16.682Z")
The local time at this server (time is in UTC).


globalLock.totalTime
14143457121
The number of microseconds since startup that the global lock was created


globalLock.lockTime
17166
The number of microseconds that the global lock has been held since it was created


globalLock.ratio
0.0000012137060870720337
The ratio between lockTime & totalTime


globalLock.currentQueue.total
12
The current number of operations queued waiting for the global lock


globalLock.currentQueue.readers
10
The current number of operations queued waiting on a read lock


globalLock.currentQueue.writers
2
The current number of operations queued waiting for a write lock


globalLock.activeClients.total
3
Total number of active clients connected to this server


globalLock.activeClients.readers
2
The total number of active clients currently performing read operations


globalLock.activeClients.writers
1
The total number of active clients currently performing write operations


mem.bits
64
Is this a 32 or 64 bit architecture?


mem.resident
20
number of megabytes resident. It is typical over time, on a dedicated database server, for this number to approach the amount of physical ram on the box.


mem.virtual
2502
virtual megabytes for the mongod process. Generally virtual should be a little larger than mapped, but if virtual is many gigabytes larger, that could indicate a memory leak - with journalling, virtual is twice mapped


mem.supported
true
Whether or not this machine supports extended memory info. If this is false, other values in 'mem' may not be present


mem.mapped
80
As MongoDB memory maps all the data files, this number is likely similar to your total database(s) size.


connections.current
23
The number of currently active connections to this server


connections.available
50
The number of available connections remaining


extra_info.heap_usage_bytes
234342
The number of bytes of heap used by this process. Only available on linux


extra_info.page_faults
2523
The number of page faults on this process. Only available on linux


indexCounters.btree.accesses
2342
The number of times the btree indexes have been accessed


indexCounters.btree.hits
2340
The number of times a btree page was in memory


indexCounters.btree.misses
2
The number of times a btree page was not in memory


indexCounters.btree.resets
0
The number of times the index counters have been reset to 0


indexCounters.btree.missRatio
0
The ratio of misses to hits on the btree


backgroundFlushing.flushes
214
The number of times the database has flushed writes to disk


backgroundFlushing.total_ms
1357
The total number of ms that the database has spent flushing data to disk


backgroundFlushing.average_ms
6.341121495327103
The average number of ms it takes to perform a single flush


backgroundFlushing.last_ms
7
The number of ms that the last flush took to complete


backgroundFlushing.last_finished
ISODate("2011-03-01T05:29:44.124Z")
The timestamp from when the last flush was completed


cursors.totalOpen
0
The total number of cursors that the server is maintaining for clients


cursors.clientCursors_size
[deprecated] Same as cursors.totalOpen


cursors.timedOut
0
The number of cursors that have timed out since this server was started


network.bytesIn
1430
The total number of bytes sent to this database


network.bytesOut
2140
The total number of bytes sent from this database


network.numRequests
20
The total number of requests that have been sent to this database


repl.setName
mySet
The name of the replica set that this server is a part of


repl.ismaster
true
Whether or not this node is the master of the replica set


repl.secondary
false
Whether or not this node is a secondary of the replica set


repl.hosts
[ "my.node.com:27017", "other.node.com:27017", "third.node.com:27017"]
The set of hosts in this replica sets


opcounters.insert
0
The total number of inserts performed since this process started


opcounters.query
9
The total number of queries performed since this process started


opcounters.update
0
The total number of updates performed since this process started


opcounters.delete
0
The total number of deletes performed since this process started


opcounters.getmore
0
The total number of times getMore has been called on any cursor since this process started


opcounters.command
13
The total number of other commands performed since this process started


asserts.regular
0
The number of regular asserts raised since this process started


asserts.warning
0
The number of warnings raised since this process started


asserts.msg
0
The number of message asserts. These are internal server errors that have a well defined text string. Stack traces are logged for these


asserts.user
0
The number of user asserts. These are errors that can be generated by a user such as out of disk space or duplicate key


asserts.rollovers
0
The number of times the assert counters have rolled over since this process started


writeBacksQueued
false
Whether or not there are any operations from a mongos that have to be retried


dur.commits
0
The number of commits to the journal that have occured in the last interval


dur.journaledMB
0
MBs of data written to the journal in the last interval


dur.writeToDataFilesMB
0
MBs of data written from journal to data files in the last interval


dur.commitsInWriteLock
0
The number of commits in the last interval which were in a write lock. Commits in a write lock are undesirable


dur.earlyCommits
0
Number of times a commit was requested before the scheduled time


dur.timeMs.dt
3011
The time length of the interval over which the dur statswere collected


dur.timeMs.prepLogBuffer
0
The amount of time spent preparing to write to the journal


dur.timeMs.writeToJournal
0
The amount of time spent actually writing to the journal


dur.timeMs.writeToDataFiles
0
The amount of time spent writing to datafiles after journaing


dur.timeMs.remapPrivateView
0
The amount of time spent remapping copy-on-write memory mapped views


ok
1
Whether or not serverStatus returned correctly

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-84395-1-1.html 上篇帖子: MongoDB的TruncationException异常解决方法 下篇帖子: MongoDB学习笔记(二)访问权限
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表