Anyone who works with mongodb and prisma came acro...
# orm-help
k
Anyone who works with mongodb and prisma came across -
Copy code
Error occurred during query execution:\nConnectorError(ConnectorError { user_facing_error: None, kind: RawDatabaseError { code: \"unknown\", message: \"Operation timed out (os error 110)\" } })
The mongodb official docs make mention of a
socketTimeoutMS
https://www.mongodb.com/docs/v5.0/reference/connection-string/#mongodb-urioption-urioption.socketTimeoutMS but they say the default is to never timeout although it might vary depending on the driver. So im wondering if the underlining driver which prisma uses has this value set and if its possible to change.
1
Also receiving
Broken pipe (os error 32)
seems like some timeout issue
j
Not familiar with this particular scenario, but in my experience timeouts & broken pipes tend to happen if there’s some kind of problem that’s causing too much data to be transmitted or the sending/receiving process to crash - have you tried running the query directly against the db using the command line or a gui mongo client?
k
I am attempting to bulk insert an array of object which is approx 14mb in size
I dont tihnk the size is the issue, there is no lag before i receive that error. It happens almost immediatly when it goes to insert
So it fetches data from a 3rd party for something like 5 mins and then inserts in bulk at once.
Ok so i found out what was the issue @Joshua Ohlman my ELB keep idle timeout was set to 60 seconds. Becuase it takes 5 minutes to fetch the data before it makes an insert, im guessing mongodb has already closed the connection to the prisma client
🙌 1
👍 1
So it pings the server periodically ...