由于字數太多了，我就貼幾個常見的日志情況。。。求大佬幫忙看看他說的啥意思？
2017-11-13T09:00:00.337+0800 I COMMAND [conn13] command ctpminutedb.l1805 command: insert { insert: "l1805", writeConcern: {}, ordered: true, documents: [ { _id: 1510297200000, exchange: "", symbol: "l1805", open: 9800.0, high: 9800.0, low: 9800.0, close: 9800.0, volume: 4.0, datetime: new Date(1510297200000), date: "2017-11-10", time: "15:00:00.0", openInterest: 158906.0 } ] } ninserted:1 keysInserted:1 numYields:0 reslen:44 locks:{ Global: { acquireCount: { r: 1, w: 1 } }, Database: { acquireCount: { w: 1 } }, Collection: { acquireCount: { w: 1 } } } protocol:op_query 109ms
類似這種日志有N多條，離崩潰時間越近這種日志越多，這是做了什么？ 是沒insert進去嗎？ 后面109MS時間是干了什么用了這么久？
2017-11-18T15:55:11.485+0800 I COMMAND [conn30] command ctpminutedb.rb1801 appName: "MongoDB Shell" command: find { find: "rb1801", filter: {}, limit: 5.0, singleBatch: false, sort: { datetime: -1.0 } } planSummary: COLLSCAN keysExamined:0 docsExamined:68222 hasSortStage:1 cursorExhausted:1 numYields:534 nreturned:5 reslen:1136 locks:{ Global: { acquireCount: { r: 1070 } }, Database: { acquireCount: { r: 535 } }, Collection: { acquireCount: { r: 535 } } } protocol:op_command 144ms
這個又是咋了 沒看太明白
2017-11-28T04:13:58.690+0800 I COMMAND [ftdc] serverStatus was very slow: { after basic: 21, after asserts: 57, after backgroundFlushing: 84, after connections: 123, after dur: 172, after extra_info: 248, after globalLock: 369, after locks: 430, after network: 430, after opLatencies: 481, after opcounters: 521, after opcountersRepl: 531, after repl: 721, after storageEngine: 831, after tcmalloc: 922, after wiredTiger: 1174, at end: 1537 }
2017-11-28T04:14:02.901+0800 I COMMAND [conn33] command admin.$cmd command: isMaster { isMaster: 1 } numYields:0 reslen:189 locks:{} protocol:op_query 498ms
2017-11-28T04:14:02.937+0800 I COMMAND [ftdc] serverStatus was very slow: { after basic: 68, after asserts: 131, after backgroundFlushing: 221, after connections: 324, after dur: 356, after extra_info: 442, after globalLock: 486, after locks: 612, after network: 655, after opLatencies: 710, after opcounters: 742, after opcountersRepl: 786, after repl: 928, after storageEngine: 1007, after tcmalloc: 1159, after wiredTiger: 1903, at end: 2582 }
2017-11-28T04:14:05.264+0800 I COMMAND [ftdc] serverStatus was very slow: { after basic: 82, after asserts: 126, after backgroundFlushing: 145, after connections: 182, after dur: 204, after extra_info: 329, after globalLock: 429, after locks: 555, after network: 573, after opLatencies: 627, after opcounters: 652, after opcountersRepl: 688, after repl: 719, after storageEngine: 743, after tcmalloc: 775, after wiredTiger: 924, at end: 1097 }
2017-11-28T04:14:09.200+0800 I COMMAND [conn38] command admin.$cmd command: isMaster { isMaster: 1 } numYields:0 reslen:189 locks:{} protocol:op_query 148ms
2017-11-28T04:14:17.644+0800 I COMMAND [ftdc] serverStatus was very slow: { after basic: 39, after asserts: 66, after backgroundFlushing: 78, after connections: 110, after dur: 110, after extra_info: 132, after globalLock: 142, after locks: 264, after network: 264, after opLatencies: 299, after opcounters: 339, after opcountersRepl: 368, after repl: 435, after storageEngine: 653, after tcmalloc: 819, after wiredTiger: 1238, at end: 1537 }
2017-11-28T04:14:19.689+0800 I COMMAND [conn38] command admin.$cmd command: isMaster { isMaster: 1 } numYields:0 reslen:189 locks:{} protocol:op_query 150ms
2017-11-28T04:14:20.163+0800 I COMMAND [ftdc] serverStatus was very slow: { after basic: 46, after asserts: 65, after backgroundFlushing: 65, after connections: 106, after dur: 124, after extra_info: 161, after globalLock: 179, after locks: 196, after network: 230, after opLatencies: 245, after opcounters: 257, after opcountersRepl: 279, after repl: 329, after storageEngine: 360, after tcmalloc: 393, after wiredTiger: 902, at end: 1066 }
2017-11-28T04:19:25.885+0800 I COMMAND [conn33] command admin.$cmd command: isMaster { isMaster: 1 } numYields:0 reslen:189 locks:{} protocol:op_query 103ms
2017-11-28T04:20:02.734+0800 I COMMAND [conn38] command admin.$cmd command: isMaster { isMaster: 1 } numYields:0 reslen:189 locks:{} protocol:op_query 274ms
2017-11-28T04:20:06.542+0800 I COMMAND [conn33] command admin.$cmd command: isMaster { isMaster: 1 } numYields:0 reslen:189 locks:{} protocol:op_query 154ms
2017-11-28T04:20:13.435+0800 I COMMAND [conn38] command admin.$cmd command: isMaster { isMaster: 1 } numYields:0 reslen:189 locks:{} protocol:op_query 112ms
2017-11-28T04:20:16.924+0800 I COMMAND [conn33] command admin.$cmd command: isMaster { isMaster: 1 } numYields:0 reslen:189 locks:{} protocol:op_query 124ms
2017-11-28T04:22:04.562+0800 I COMMAND [conn38] command admin.$cmd command: isMaster { isMaster: 1 } numYields:0 reslen:189 locks:{} protocol:op_query 126ms
后面就不停的重復這些了，說性能低，但是沒明白為什么會造成這樣 ，求大佬幫忙看看這些日志是想說啥意思 或者能不能給個鏈接，isMaster protocol:op_query 啥的我都沒見過不知道如何下手去查，百度也沒搜到
uj5u.com熱心網友回復：
能正常啟動嗎uj5u.com熱心網友回復：
是不是從機復制速度跟不上了？斷開復制看看uj5u.com熱心網友回復：
可以正常啟動，我用自己電腦看了一下 就沒事，我感覺可能是虛擬機記憶體太小了？
uj5u.com熱心網友回復：
我用自己電腦看了一下 就沒事，我感覺可能是虛擬機記憶體太小了？
uj5u.com熱心網友回復：
據說mongodb對記憶體要求很高據說mongodb對記憶體要求很高，你的猜測看起來是很有道理的
轉載請註明出處，本文鏈接：https://www.uj5u.com/shujuku/103715.html
標籤：MongoDB