.NET Core 3.1中MongoDB MongoClientSettings配置咨询：waitQueueSize弃用后的替代方案及参数迁移方法

Hey Dave,

Great question—this is a common point of confusion since the MongoDB .NET driver deprecated WaitQueueSize in version 2.12.3. Let's walk through the right way to adjust your configuration.

What's the replacement? #

The driver team deprecated WaitQueueSize because fixed queue sizes can lead to unpredictable behavior under load. Instead, they recommend using WaitQueueTimeout to control how long your application waits for a connection from the pool before throwing an exception. This is a more intuitive and reliable approach than limiting the number of waiting requests.

How to update your code #

Your original code was setting WaitQueueSize using a waitQueueMultiple value (which is typically a multiplier of MaxConnectionPoolSize). Here's how to refactor it to use the recommended approach:

var url = new MongoUrl(_mongoDbConfiguration.ConnectionString);
var settings = MongoClientSettings.FromUrl(url);

// Keep your existing MaxConnectionPoolSize configuration
settings.MaxConnectionPoolSize = _mongoDbConfiguration.MaxPoolSize;

// Replace WaitQueueSize with WaitQueueTimeout
// Adjust the timeout value based on your application's tolerance for waiting
// Example: Allow waiting up to 30 seconds for a connection
settings.WaitQueueTimeout = TimeSpan.FromSeconds(_mongoDbConfiguration.WaitQueueTimeoutSeconds);

var client = new MongoClient(settings);
var database = client.GetDatabase(url.DatabaseName);
return database;

Key notes: #

• If you previously used waitQueueMultiple to calculate WaitQueueSize (e.g., WaitQueueSize = MaxConnectionPoolSize * waitQueueMultiple), you'll need to translate that into a timeout value that makes sense for your workload. For example, if your app could handle 5x the pool size waiting, set a timeout that gives enough time for connections to become available under normal load (30-60 seconds is a common starting point).
• The WaitQueueTimeout setting ensures your app won't hang indefinitely waiting for a connection—instead, it throws a MongoWaitQueueTimeoutException if the timeout is exceeded, letting you handle the failure gracefully.

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