title: Why does a query in mongodb run only for exaclty 3600s and then stops without any logs?
body: <p>I use a find command to parse my initial json files into a new collection. All works really great but it stops at exactly 3600s. It is not a hardware issue since I tried on two different machines.
  I use a
      db.collection.find().forEach( function ... command.</p>
  
  <p>I use robomongo as a temporary gui.</p>
  
  <p>EDIT: I also have the following entry in my logs
  <a href="https://stackoverflow.com/questions/31729358/conn557392-killcursors-found-0-of-1-in-mongodb-replication-primary-log">&quot;[conn557392] killcursors: found 0 of 1&quot; in Mongodb replication primary log</a></p>
  
  <p>EDIT: Solved! This seems to be a problem with robomong. Works fine in the normal mongo shell.</p>