QueryStream ending early, after only 1/14 of the query result set

I have a collection with 700K+ records. It contains a legacy geo-location field and I wrote a script, using a QueryStream, to update the field into a GeoJSON compatible format.

The problem is that when using a QueryStream, the stream is ended after only 50635 documents.

The script code is as follows:

var stream = db.propertyModel.find()
.where("address.location").exists(true)
.where("address.location.type").exists(false)
.select("address.location")
.stream();

var count = 0;
stream.on("data", function(property) {
  stream.pause();

  var location = {
    type: "Point",
    coordinates: property.address.location
  };

  property.update({ $set: { "address.location": location }}).exec(function(err, numberAffected, rawResponse) {
    if (err) {
      console.log("\n" + err.message);
    }

    count += 1;
    util.print("\rUpdated property # " + count);

    stream.resume();
  });
}).on("error", function(err) {
  console.log(err);
}).on("close", function() {
  db.mongoose.disconnect();
  console.log("\nStream closed\n");
});

From the Mongo shell, I have confirmed that the same query has a count of 721,938 documents:

db.properties.count({ "address.location": { $exists: true }, "address.location.type": { $exists: false }})

Response: 721938

Why is the QueryStream only streaming 50635 documents? Is it an internal cursor limitation?

[rickhuizinga]

I’ve found the solution for long running cursors: the timeout option needs to be set to false.

Calling setOptions({ timeout: false }) on the query prior to calling stream() will prevent long-running streams from terminating prematurely.

[vkarpov15]

@rickhuizinga thanks!