Error that hasn't been happening before (started 2 days ago)

I’ve been having this error pop up on me recently :

MongooseError: Operation importantids.findOne() buffering timed out after 10000ms at Timeout.<anonymous> (/root/disgo/node_modules/mongoose/lib/drivers/node-mongodb-native/collection.js:198:23) at listOnTimeout (node:internal/timers:557:17) at processTimers (node:internal/timers:500:7)

I successfully connect to the database and interact with it in my app, but recently, it keeps doing that error at random times and will not stop until I restart the app.

Mongoose version : 5.13.7 (won’t update using npm update)

[vkarpov15]

I took a closer look and I don’t see anything to indicate this is anything other than a case of replica set hostname inconsistency, which is documented and expected behavior in the MongoDB Node driver. You need to make sure that the self-reported hostname on the machine that’s hosting your MongoDB server is resolvable from your application server.

[fakelag]

Can second this. For me the issue seems to be that the new mongoose version (we are using 6.1.6) tries to resolve the replica set hostname by itself and throws getaddrinfo ENOTFOUND mongod-0 (mongod-0 is resolvable from the mongodb server, but not from connecting client). However previous versions and mongosh connects fine. It can not connect and so buffered operations fail with timeout.

Fixed by setting directConnection: true in mongoose connection options like so. It feels like previous versions potentially had the connection default to direct connect or something similar?

    const connectionPromise = mongoose.connect(mongoUrl, {
        directConnection: true,
    });