MongoError: cursor does not exist, was killed or timed out

Question

I keep getting this error when I try to retrieve data from the CosmoDB..

I have tried to set timeout:true/false and try,, but I still keep getting the same response

{"name":"MongoError","message":"cursor does not exist, was killed or timed out"}

Answer 1

Hello,

Please check these links - 

https://mongodb.github.io/node-mongodb-native/api-generated/collection.html#findhttps://mongodb.github.io/node-mongodb-native/api-generated/collection.html#find

https://stackoverflow.com/questions/30856321/node-js-mongodb-mongoerror-cursor-killed-or-timed-out

---

Please Mark as Answer if my post works for you or Vote as Helpful if it helps you. Kapil Singh

Answer 2

I am able to overcome the issue by setting a 'limit' to the transaction.. but its not a solution.. 

Answer 3

@SharanthSrinivasan, the support for MongoDB cursors is not turned on by default as it requires another collection (with 400 RUs) provisioned. Use the feedback email [e-mail] to request this change and include your subscription/account if you really need it.

Answer 4

Hi,

I m facing the exact same problem. The MongoError only appears on collection with a lot of data. It is fixed by setting a limit, but I need to retrieve the whole table in order to deal with the data.

"the support for MongoDB cursors is not turned on by default as it requires another collection (with 400 RUs) provisioned"

Can you please help me with this setting you mention above? If I have access to the Azure Cosmos DB account of the MongoDB, can I set it myself or I still need to send an email to [e-mail]??


Thanks in advance for your response.

Answer 5

Yes, send your account name to [e-mail] to enable server-side cursor.

Answer 6

Hi there,

I am having same issue, 

Can I send my email

Thanks

Andy