Server Status Very Slow

221 views

Skip to first unread message

Rafael Pereira Silva

unread,

Aug 21, 2017, 6:23:17 PM8/21/17

to mongodb-user

Hello, I have a problema with mongoDB.

An message in log:

[ftdc] serverStatus was very slow: { after basic: 0, after asserts: 0, after backgroundFlushing: 0, after connections: 0, after dur: 0, after extra_info: 923, after globalLock: 923, after locks: 923, after network: 923, after opLatencies: 923, after opcounters: 923, after opcountersRepl: 923, after repl: 923, after security: 923, after storageEngine: 923, after tcmalloc: 923, after wiredTiger: 923, at end: 1766 }

Server load has gone up.

I did not find any other offenders.

Does anyone know what can it be?

Is there any way for me to check which mongo process/query did this?

thanks

Kevin Adistambha

unread,

Sep 10, 2017, 11:32:42 PM9/10/17

to mongodb-user

Hi,

Server load has gone up.
I did not find any other offenders.

Could you elaborate on what you mean? The serverStatus is very slow message typically means that the server is under heavy load, but this information alone doesn’t provide any hint as to what is happening. There could be many reasons for performance issues, such as slow disk, high pressure on the WiredTiger cache (if you’re using WiredTiger), other processes in the host competing with MongoDB on resources, multiple MongoDB processes on the server competing with each other on resources, under-provisioned servers, inefficient queries, etc.

Is there any way for me to check which mongo process/query did this?

An initial suggestion I can give is to peruse the MongoDB Diagnostics page. You may be able to check if any query exceeds the slow query threshold (100ms by default), which will be recorded in the mongod logs. You can also use the db.currentOp() command to discover currently running queries, and whether any of them has been running for an extended period.