[SERVER-67182]  Cannot run getMore on cursor 6353724926596320531 without an lsid // Node driver 4..7.0 Created: 10/Jun/22  Updated: 20/Sep/22  Resolved: 20/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 5.0.8
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: ricky work Assignee: Edwin Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

with node driver (4.7.0)and local mongo instance(5.0.8)community

 

associated code:
 .get(async(req, res) =>

{         let query = String(req.query.custom);         let x = imsColl.find(\{'fileOrientation':query}

).toArray();
      console.log((await x).length)    
     })
 

Participants:

 Description   

full error: 

C:\Users\ericcoh\Projects\privateTest\node_modules\mongodb\lib\cmap\connection.js:210
                    callback(new error_1.MongoServerError(document));
                             ^

MongoServerError: Cannot run getMore on cursor 6353724926596320531, which was created in session 9248a52d-57c5-47db-bf9d-1efa9ebf9474 - 47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=, without an lsid
    at Connection.onMessage (C:\Users\ericcoh\Projects\privateTest\node_modules\mongodb\lib\cmap\connection.js:210:30)
    at MessageStream.<anonymous> (C:\Users\ericcoh\Projects\privateTest\node_modules\mongodb\lib\cmap\connection.js:63:60)
    at MessageStream.emit (node:events:527:28)
    at processIncomingData (C:\Users\ericcoh\Projects\privateTest\node_modules\mongodb\lib\cmap\message_stream.js:132:20)
    at MessageStream._write (C:\Users\ericcoh\Projects\privateTest\node_modules\mongodb\lib\cmap\message_stream.js:33:9)
    at writeOrBuffer (node:internal/streams/writable:389:12)
    at _write (node:internal/streams/writable:330:10)
    at MessageStream.Writable.write (node:internal/streams/writable:334:10)
    at Socket.ondata (node:internal/streams/readable:754:22)
    at Socket.emit (node:events:527:28) {
  ok: 0,
  code: 50737,
  codeName: 'Location50737',
  [Symbol(errorLabels)]: Set(0) {}
}

 

associated code:
 .get(async(req, res) =>

{         let query = String(req.query.custom);         let x = imsColl.find(\{'fileOrientation':query}

).toArray();
      console.log((await x).length)    
     })
 
more info: this query should have 89 documents in it each has a few strings for some info and a binary entry of 5-6 mb . 
 
i have no idea why its doing this i see that this was an issue a few years ago but those tickets show a status of fixed.  
any help would be appriciated.



 Comments   
Comment by Edwin Zhou [ 20/Sep/22 ]

We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Comment by Edwin Zhou [ 07/Sep/22 ]

Hi rickywork2788@gmail.com

We still need additional information to diagnose the problem. I'm providing an updated upload portal for you. If this is still an issue, would you please archive (tar or zip) and upload to that link for each node in the replica set spanning a time period that includes the incident:

  • the mongod logs
  • the $dbpath/diagnostic.data directory (the contents are described here)

Best,
Edwin

Comment by Edwin Zhou [ 06/Jul/22 ]

Hi rickywork2788@gmail.com,

Thank you for your report. Can you please provide some more information about the problem you're seeing? I've created a secure upload portal for you. Files uploaded to this portal are hosted on Box, are visible only to MongoDB employees, and are routinely deleted after some time.

For each node in the replica set spanning a time period that includes the incident, would you please archive (tar or zip) and upload to that link:

  • the mongod logs
  • the $dbpath/diagnostic.data directory (the contents are described here)

Best,
Edwin

Generated at Thu Feb 08 06:07:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.