It is quite possible that none of your jobs is doing any database operation
at that particular time when you are seeing 0 operations in mongostat
results. They may be waiting for some resource or event for further
Moreover, mongostat output provides the count of database operations such
as insert, query, update, etc. and by default runs every one second. This
may not reflect all the statistics such as lock queues, cursors,
connections and storage engine level metrics. db.serverStatus()
<https://docs.mongodb.com/manual/reference/command/serverStatus/> should be
a better way of checking all statistics. You can use a small script to run
the command repeatedly and see the results. mongod logs can also help in
identifying the queries running at the time. For additional monitoring,
please also read Monitoring for MongoDB
If you still doubt that the mongodb server is waiting and not performing
the operations, please also consider providing below details for better
- Version of MongoDB that you are using.
- Storage engine that you are using
- Deployment topology (Standalone/Replica Set/Sharded cluster)
- What operations are the jobs performing on the database and their
- Output of mongostat, serverStatus and mongod logs during this time.
You received this message because you are subscribed to the Google Groups "mongodb-user"