随机出现MongoServerSelectionError连接超时问题求助

环境信息 #

• 部署平台：Vercel
• 数据库：MongoDB Atlas（免费版）
• Node.js版本：18.16.1
• Next.js版本：13
• mongodb包版本：5.8.1

错误日志 #

ERROR   Unhandled Promise Rejection     {"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"MongoServerSelectionError: connection timed out","reason":{"errorType":"MongoServerSelectionError","errorMessage":"connection timed out","reason":{"type":"ReplicaSetNoPrimary","servers":{},"stale":false,"compatible":true,"heartbeatFrequencyMS":10000,"localThresholdMS":15,"setName":"Cluster0-shard-0","maxElectionId":null,"maxSetVersion":null,"commonWireVersion":0,"logicalSessionTimeoutMinutes":null},"stack":["MongoServerSelectionError: connection timed out","    at Timeout._onTimeout (/var/task/node_modules/mongodb/lib/sdam/topology.js:278:38)","    at listOnTimeout (node:internal/timers:569:17)","    at process.processTimers (node:internal/timers:512:7)"]},"promise":{},"stack":["Runtime.UnhandledPromiseRejection: MongoServerSelectionError: connection timed out","    at process.<anonymous> (file:///var/runtime/index.mjs:1186:17)","    at process.emit (node:events:525:35)","    at emit (node:internal/process/promises:149:20)","    at processPromiseRejections (node:internal/process/promises:283:27)","    at process.processTicksAndRejections (node:internal/task_queues:96:32)"]}
[ERROR] [1692852863980] LAMBDA_RUNTIME Failed to post handler success response. Http response code: 400.
RequestId: 971d9da3-a51d-4511-a561-22d5702be848 Error: Runtime exited with error: exit status 128

错误发生时，服务器返回HTTP 500状态码。

连接代码 #

import { MongoClient } from "mongodb";

//mongodb+srv://sjhfjhfjhf/ongodb.net/awesomedb?serverSelectionTimeoutMS=60000
const uri = process.env.MONGODB_URI;
const options = {
  //useUnifiedTopology: true,
  useNewUrlParser: true,
  serverSelectionTimeoutMS: 59000,
};

let client;
let clientPromise;

if (!process.env.MONGODB_URI) {
  throw new Error("Please add your Mongo URI to .env.local");
}

if (process.env.NODE_ENV === "development") {
  // In development mode, use a global variable so that the value
  // is preserved across module reloads caused by HMR (Hot Module Replacement).
  if (!global._mongoClientPromise) {
    client = new MongoClient(uri, options);
    global._mongoClientPromise = client.connect();
  }
  clientPromise = global._mongoClientPromise;
} else {
  // In production mode, it's best to not use a global variable.
  client = new MongoClient(uri, options);
  clientPromise = client.connect();
}

// Export a module-scoped MongoClient promise. By doing this in a
// separate module, the client can be shared across functions.
export default clientPromise;

查询代码 #

import { ObjectId } from 'mongodb';
import clientPromise from '../../lib/mongodb'
import { connectToDatabase, slugify } from './blog';

export async function saveAdToMongoDB(adObj) {
  try {
    const collection = (await clientPromise).db().collection("ads");  
    let catslug = slugify(adObj.businessCategory)
    let slug = slugify( adObj.businessName + "-" + adObj.city + "-" + catslug)
    adObj.slug = slug ;
    adObj.catslug = catslug;
    let advertisementObject = {...adObj, status:"pending",image:""}
    let result = await collection.insertOne(advertisementObject);
  } catch (err) {
    console.error("Failed to save ad to MongoDB:", err);
  } 
}

用户疑问：该问题由什么原因导致？是否与MongoDB Atlas免费版有关？已升级mongodb和nextjs包，排除防火墙和IP白名单问题。

核心原因 #

1. MongoDB Atlas免费版资源限制
   免费版M0集群的CPU、内存、IOPS均有严格上限，当并发请求增加或集群进行内部维护（如节点选举、备份）时，会出现连接超时或无法选中主节点的情况，这是ReplicaSetNoPrimary错误的常见诱因。

2. Vercel无服务器函数的连接管理问题
   Vercel的Serverless函数按需启动，冷启动时会重新创建MongoDB连接；而当前生产环境代码每次都新建MongoClient并调用connect()，未复用连接池，频繁的连接创建/销毁会加剧Atlas资源消耗，提升超时概率。

3. 连接配置不完善
   代码中注释掉了useUnifiedTopology: true，虽然后续mongodb版本默认启用，但显式配置可避免兼容性问题；同时缺少连接池相关配置（如maxPoolSize），无法有效管控连接数。

解决方案 #

1. 优化MongoDB连接复用 #

修改生产环境连接逻辑，复用连接池而非每次新建客户端：

// ... 其他代码不变
if (process.env.NODE_ENV === "development") {
  if (!global._mongoClientPromise) {
    client = new MongoClient(uri, options);
    global._mongoClientPromise = client.connect();
  }
  clientPromise = global._mongoClientPromise;
} else {
  // 生产环境复用全局连接，减少冷启动时的连接创建
  if (!global._mongoClientPromise) {
    client = new MongoClient(uri, options);
    global._mongoClientPromise = client.connect();
  }
  clientPromise = global._mongoClientPromise;
}
// ...

Vercel同实例内的Serverless函数会复用全局变量，以此降低连接创建频次。

2. 完善连接配置 #

更新options，补充必要配置项：

const options = {
  useNewUrlParser: true,
  useUnifiedTopology: true, // 显式启用，确保兼容副本集模式
  serverSelectionTimeoutMS: 59000,
  maxPoolSize: 10, // 根据并发量调整，免费版建议不超过20
  minPoolSize: 1,
  heartbeatFrequencyMS: 5000, // 缩短心跳间隔，更快检测节点状态
};

3. 添加连接超时重试逻辑 #

在查询代码中增加重试机制，应对临时连接问题：

export async function saveAdToMongoDB(adObj, retryCount = 3) {
  try {
    const collection = (await clientPromise).db().collection("ads");  
    // ... 原有业务逻辑
    let result = await collection.insertOne(advertisementObject);
    return result;
  } catch (err) {
    if (err.name === 'MongoServerSelectionError' && retryCount > 0) {
      // 遇到连接超时，最多重试3次
      console.log(`连接超时，剩余重试次数：${retryCount - 1}`);
      await new Promise(resolve => setTimeout(resolve, 1000));
      return saveAdToMongoDB(adObj, retryCount - 1);
    }
    console.error("Failed to save ad to MongoDB:", err);
    throw err; // 抛出错误让上层处理，避免静默失败
  } 
}

4. 监控Atlas集群状态 #

登录MongoDB Atlas控制台查看Metrics面板，关注CPU使用率、连接数、IOPS等指标。若频繁触达免费版限制，可考虑升级到M10及以上版本，或优化查询逻辑、减少不必要的数据库操作。

总结 #

该问题与MongoDB Atlas免费版的资源限制直接相关，同时Vercel无服务器环境下的连接管理不当加剧了问题。通过优化连接复用、完善配置和添加重试逻辑，可显著降低错误发生概率；若业务量持续增长，升级Atlas套餐是彻底解决的方案。

内容的提问来源于stack exchange，提问作者user2298124