Info
Our development environment uses a one node replica set running mongo 4.0.7.
During a data load we create a new document. We can initially find this document with a simple query, but straight afterwards when we run the same query from within a transaction we cannot find the document.
Top User Comments
carl.champain commented on Tue, 19 Nov 2019 16:07:37 +0000:
dave.shaw@ripjar.com, I'm not sure wether you saw my previous comment or not (I had to edit it, sorry about that!), but this ticket doesn't appear to be a bug. So if you need assistance troubleshooting, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag.
dave.shaw@ripjar.com commented on Tue, 19 Nov 2019 15:39:08 +0000:
Hi Carl,
I've attached the mongo log file. I've had to sanitise it a little bit as it contains some sensitive company data.
The two queries were identical and a sample looked like this:
`{"namespace":"torch","clientKey":"lowercasekey","id":83372}`
Additionally, when we changed the write concern in the document creation command to include `{j:true}` we did not see this problem.
imongo.clean.log
Dave
carl.champain commented on Tue, 19 Nov 2019 15:14:30 +0000:
Hi dave.shaw@ripjar.com,
The SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need assistance troubleshooting, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag.
A good rule of thumb, when asking for help to our community, is to provide details about your issue. For example, in your case, you could provide both queries and the mongod.log file for this node.
Kind regards,
Carl
