StackExchange.Redis日志中mc参数含义解析及低负载下随机崩溃问题排查求助

Hey there! Let's break this down for you—first, we'll clarify that mysterious mc log parameter, then dig into why your Redis calls are timing out during low-traffic windows, and wrap up with concrete fixes to try.

What Does mc: 1/1/0 Mean? #

That mc field stands for Multiplexer Connection Stats, and the three numbers represent:

• 1: The number of currently active, connected Redis connections
• 1: The total number of connections configured in your multiplexer's connection pool
• 0: The number of connections currently in the process of being established (pending)

In your case, this tells us you have exactly one active connection (matching your pool size) and no pending connections being set up. On its own, this is normal—but when paired with other log details, it helps paint the picture of what's going wrong.

Why Are You Seeing Timeouts During Low Load? #

The biggest clue in your log is bw: SpinningDown. This means the StackExchange.Redis connection multiplexer is actively shrinking the number of idle connections in the pool to save resources—this behavior is designed for low-traffic periods like your 6AM window.

The problem happens when a request comes in right as connections are being spun down: the multiplexer might not have an available connection ready to handle the request immediately, leading to that 5-second timeout you're seeing.

Another red flag is POOL: (Threads=2,QueuedItems=1757,CompletedItems=382420032)—your application's thread pool has a backlog of 1757 queued tasks even though only 2 threads are active. During low load, the thread pool shrinks to its minimum size, and when requests do come in, there's a delay spinning up new threads to handle them. This compounds the Redis connection issue, making timeouts more likely.

Actionable Fixes to Resolve the Timeouts #

• Adjust Redis Connection Pool Idle Settings
  Prevent the multiplexer from aggressively closing idle connections by setting a minimum number of idle connections to keep alive. This ensures there's always a ready connection for unexpected requests during low load. Here's how to configure it:

  var redisConfig = ConfigurationOptions.Parse("your-redis-server-endpoint");
  redisConfig.MinIdleConnections = 2; // Keep at least 2 connections idle
  var multiplexer = ConnectionMultiplexer.Connect(redisConfig);
  

• Tune Your Application's Thread Pool Minimums
  Increase the minimum number of worker and IOCP threads to avoid delays in spinning up threads when traffic picks up slightly during low-load periods. Add this code early in your application startup (before initializing Redis):

  // Adjust these numbers based on your app's needs—start small and monitor
  ThreadPool.SetMinThreads(10, 10);
  

• Verify Redis Server Idle Timeout Configuration
  Check if your Redis server is closing idle connections too quickly. Run the CONFIG GET timeout command on your Redis server—if it's set to a short value (not 0, which means no timeout), it might be dropping connections during low traffic, forcing the multiplexer to re-establish them on demand (which can cause delays).

• Upgrade StackExchange.Redis
  Your current version (v2.6.48) is a bit outdated. Newer versions (especially v2.7 and above) include improvements to connection management during low-load periods, including better handling of connection spinning down and thread pool interactions. Upgrading could resolve the issue without needing to tweak configurations.

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