-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection timeout 10000ms when upgraded mongoose from 7.4.5 to 8.7.1 #14971
Comments
We're also experiencing a very similar issue. Using MongoDB Server 8.0 in Atlas and locally in Docker. Everything works intermittently, but lots of buffering error across lots of different find’s and aggregates in all of our microservices.
Posted about it here: https://www.mongodb.com/community/forums/t/buffering-timed-out-after-10000ms-8-7-0-mongoose-node-20-10-0/299932 |
We found the issue was introduced in 8.7. We were on 8.6, but only saw the issues when we upgraded to 8.7. |
the same issue.
|
The "Buffering timed out after 10000ms" is indicative of Mongoose not being connected to MongoDB. Here's a couple of suggestions you can try:
const db = await mongoose.connect(uri, { serverSelectionTimeoutMS: 5000 });
mongoose.set("strictQuery", false);
const dbConnect = async () => {
if (mongoose.connection.readyState === 1) {
return;
}
await mongoose.connect(uri);
};
export default dbConnect; You can read more on our Lambda docs |
My error got resolved somehow when I used these: const options = { Please check. |
This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days |
We are also facing the same issue, which only happens in the production environment. We have tried multiple versions after 8.7.1 and none of them seems to be working so far. We are stuck at using 8.6.x as of now. Another thing to point out is that we have about 15 services and all of them fail when we go to 8.7.1 or above and that too only in production. |
hi.. did you check with latest version ie 8.8.2? |
I have the same issue. Downgrading to mongoose 8.6.x solved the issue. I tried everything, even created a new mongodb atlas cluster to make sure it's not the cluster, even though connecting to the db worked fine from other tools. There's definitely something wrong with mongoose or the mongodb package. Worth mentioning: It only fails to connect with the mongodb+srv:// scheme.
I did, no success. |
Prerequisites
Mongoose version
8.7.1
Node.js version
20.x
MongoDB version
6.9
Operating system
None
Operating system version (i.e. 20.04, 11.3, 10)
No response
Issue
Last night, I upgraded my mongodb and mongoose from versions 5.8.1 to 6.9 and. 7.4.5 to 8.7.1 respectively.
I tested on my local. Everything worked fine. I promoted the changes to test env - AWS amplify - things were fine. Then, I moved the changes to production.
My db is hosted on mongo atlas serverless cluster.
On production, sometimes same queries will work fine but other times give timeout error with 10000ms. I mean same queries behaving differently.
I have been scratching my head because both test and prod env are exactly similar except that prod is connected to my domain name.
Please assist if someone has knowledge about this.
sharing my connection code and one query that fails/passes abruptly.
The text was updated successfully, but these errors were encountered: