作者:snail | 来源:互联网 | 2023-06-02 18:47
mongodb服务在进行定时任务操作时崩溃,查询日志发现崩溃时固定出现以下两条格式的记录:1234567command admin.$cmd command: isMaster { ismaster:
mongodb服务在进行定时任务操作时崩溃,查询日志发现崩溃时固定出现以下两条格式的记录:
1 2 3 4 5 6 7
| command admin.$cmd command: isMaster { ismaster: 1 } numYields:0 reslen:189 locks:{} protocol:op_query 1600ms
serverStatus was very slow: { after basic: 600, after asserts: 1001, after backgroundFlushing:
1302, after connections: 1701, after dur: 2194, after extra_info: 3300, after globalLock: 3995,
after locks: 5002, after network: 5304, after opLatencies: 5600, after opcounters: 5799,
after opcountersRepl: 6104, after repl: 6500, after security: 6802, after storageEngine: 7500,
after tcmalloc: 8601, after wiredTiger: 32799, at end: 37100 } |
从服务器的log来看,mongodb崩溃时进行了大量的读操作。
想请教各位大佬如何从这两条分析mongodb服务崩溃的原因?
另外前一条让我很困惑。我们并没有为mongodb设置副本集,为什么还会有isMaster的命令呢?