1

I'm in the process of migrating an old mongoDB database. Before shutting down the old one, I want to make sure nothing is still writing to it or reading from it. Looking at Compose's MongoDB classic monitoring tool, the graph indicates 0 inserts, 0 queries, 0 updates and 0 deletes BUT, also a steady stream of "getMores" and "commands".Compose's graph

I assume the commands must be internal processes of MongoDB, but which ones? What's going on? Also, from the bit of search I've made, it seems that getMores have something to do with cursors, what internal process would be using cursors?

  • What is your MongoDB deployment architecture? Is it a standalone, Replica set or Sharded cluster? Also please check this out stackoverflow.com/a/21660653/3432487 – Mani Jun 17 at 15:44
  • Thanks for that link! The DB does have a Replica Set. – FelDev Jun 17 at 17:25
  • 2
    Since this is a replica set, the getMores are likely due to replication. Even with no write activity, replica set members will poll for updates on the oplog.rs collection. The commands are probably related to monitoring (for example, serverStatus to get the opcounters that are being plotted). – Stennie Jun 18 at 17:57
0

Since this is a replica set, the getMores are likely due to replication. Even with no write activity, replica set members will poll for updates on the oplog.rs collection.

The commands are probably related to monitoring (for example, serverStatus to get the opcounters that are being plotted).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.