title: MongoError: connection destroyed, not possible to instantiate cursor
body: <p>While running an app on Heroku, using Parse-Server with mLab, I am getting the following error in the logs:</p>
  
  <pre><code>app[web.1]: /app/node_modules/parse-server/lib/ParseServer.js:481
  app[web.1]:             throw err;
  app[web.1]:             ^
  app[web.1]: MongoError: connection destroyed, not possible to instantiate cursor
  app[web.1]:     at nextFunction (/app/node_modules/mongodb-core/lib/cursor.js:607:55)
  app[web.1]:     at Cursor.next [as _next] (/app/node_modules/mongodb-core/lib/cursor.js:692:3)
  app[web.1]:     at fetchDocs (/app/node_modules/mongodb/lib/cursor.js:856:10)
  </code></pre>
  
  <p>To make things even more complicated, I do not get it all the time, while the same code is running.</p>
  
  <p>After searching on the web I read that it happens when trying to read more than 100 records from the database.
  This seems consistent with what I am observing.</p>
  
  <p>Unfortunately I did not find any solution to the problem on the web.
  Therefore my question: How can I handle this issue?</p>
  
  <p>Is there any way to raise the threshold from 100 to a higher value?
  Or any other good way to deal with this problem?</p>
  
  <p>In case this may be useful here the code for the function doing the job.
  It works like charm in most cases.
  When the typKey provided happens to match too many records, I get the problem above mentioned.</p>
  
  <pre><code>function get_List(displayPage, db, response) {
    db.collection('TheCollection', function (err, collection) {
      collection.find({"typeKey": "TYPE01"}).toArray(function(err, items) {
        if(err) throw err;
  
        response.render('pages/displayList.ejs', {
          dataArray: items
        });
      });
    });
  }
  </code></pre>