-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Critical - P2
-
None
-
Affects Version/s: None
-
Component/s: None
-
Empty show more show less
We are in the process of moving from a single replica set to a sharded database. After the converstion, we've started intermittently seeing these errors:
MongoError: Cursor not found (namespace: 'liveearth.hallMonitorCollectors', id: 5109468296066159828).
at /usr/src/app/node_modules/mongodb-core/lib/connection/pool.js:593:63
at authenticateStragglers (/usr/src/app/node_modules/mongodb-core/lib/connection/pool.js:516:16)
at Connection.messageHandler (/usr/src/app/node_modules/mongodb-core/lib/connection/pool.js:552:5)
at emitMessageHandler (/usr/src/app/node_modules/mongodb-core/lib/connection/connection.js:309:10)
at Socket.<anonymous> (/usr/src/app/node_modules/mongodb-core/lib/connection/connection.js:452:17)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at TCP.onread (net.js:635:20)
This happens multiple different collections (which are not sharded). It happens most frequently on the collection listed in the stack trace above which has 281 documents and is 568Kb.
Important details:
- Mongo v3.6.3
- Node driver v3.0.10
- Node v10.4.1 (running on alpine)
What other information can I provide?
- related to
-
-
- Closed
-