Skip to content
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

Open
1 task done
sukhminderx opened this issue Oct 17, 2024 · 9 comments
Open
1 task done
Labels
help wanted help This issue can likely be resolved in GitHub issues. No bug fixes, features, or docs necessary

Comments

@sukhminderx
Copy link

Prerequisites

  • I have written a descriptive issue title

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.

import { ServerApiVersion } from "mongodb";
import mongoose from "mongoose";

const uri = process.env.MONGODB_URI as string;


const connection: {
  isConnected?: boolean;
} = {};

const dbConnect = async () => {
  if (connection.isConnected) return;
  mongoose.set("strictQuery", false);
  const db = await mongoose.connect(uri);

  connection.isConnected = Boolean(db.connections[0].readyState);
};
export default dbConnect;
export async function GET(req: Request) {
  try {
    await apiHandler(req, "");
    const countries: any = await Countries.find({}).exec();
    return NextResponse.json(countries, { status: 200 });
  } catch (error: any) {
    console.log("wb saas: countries");
    console.log(
      typeof error !== "string"
        ? error.message
          ? error.message
          : (error || {}).toString()
        : error
    );
    return errorHandler(error);
  }
}
@sukhminderx sukhminderx added help This issue can likely be resolved in GitHub issues. No bug fixes, features, or docs necessary help wanted labels Oct 17, 2024
@vkarpov15 vkarpov15 added this to the 8.7.3 milestone Oct 20, 2024
@garethlowriehive
Copy link

garethlowriehive commented Oct 22, 2024

We're also experiencing a very similar issue.

Using MongoDB Server 8.0 in Atlas and locally in Docker.
Node: 20.11.1
Mongoose 8.7.1

Everything works intermittently, but lots of buffering error across lots of different find’s and aggregates in all of our microservices.

Buffering timed out after 10000ms

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

@ksmithut
Copy link

ksmithut commented Oct 24, 2024

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.

@vkarpov15 vkarpov15 modified the milestones: 8.7.3, 8.7.4 Oct 25, 2024
@slavik-pastushenko
Copy link

slavik-pastushenko commented Oct 30, 2024

the same issue.
Mongo: 8.0
Node: 20.13.1
Mongoose 8.7.1

Buffering timed out after 10000ms

@vkarpov15
Copy link
Collaborator

The "Buffering timed out after 10000ms" is indicative of Mongoose not being connected to MongoDB. Here's a couple of suggestions you can try:

  1. Reduce your serverSelectionTimeoutMS. This will likely just change the error message, but the new error message will provide a little bit more info on why you can't connect to MongoDB:
const db = await mongoose.connect(uri, { serverSelectionTimeoutMS: 5000 });
  1. Fix your isConnected logic. isConnected is not tied to Mongoose's readyState, if Mongoose's readyState changes then isConnected is still tied to the initial value. Try the following instead.
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

@vkarpov15 vkarpov15 removed this from the 8.8.1 milestone Nov 1, 2024
@sukhminderx
Copy link
Author

My error got resolved somehow when I used these:

const options = {
serverApi: {
version: ServerApiVersion.v1,
strict: true,
deprecationErrors: true,
},
};

Please check.

Copy link

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

@github-actions github-actions bot added the Stale label Nov 18, 2024
@tabz24
Copy link

tabz24 commented Nov 19, 2024

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.

@sukhminderx
Copy link
Author

hi.. did you check with latest version ie 8.8.2?

@github-actions github-actions bot removed the Stale label Nov 20, 2024
@VanCoding
Copy link

VanCoding commented Nov 21, 2024

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.

@sukhminderx

hi.. did you check with latest version ie 8.8.2?

I did, no success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted help This issue can likely be resolved in GitHub issues. No bug fixes, features, or docs necessary
Projects
None yet
Development

No branches or pull requests

7 participants