365 — TemporarilyUnavailable

performanceconcurrencystorage

The operation was rejected because the server is temporarily overloaded

What is happening?

TemporarilyUnavailable is returned when the server cannot service a request because a concurrency control resource is exhausted. This typically means all available WiredTiger read or write tickets are in use, or the execution control mechanism is throttling new admissions. Introduced in MongoDB 6.0, it replaces situations that previously caused operations to stall indefinitely under heavy load.

Common causes

  1. All WiredTiger write tickets are held by concurrent operations
  2. Extremely high write throughput saturating the storage engine
  3. Long-running transactions holding tickets for extended periods
  4. Server under heavy CPU or I/O pressure from index builds or compaction
  5. Insufficient WiredTiger cache causing excessive eviction contention

Source code references

ErrorCodes::TemporarilyUnavailable found in 19 locations in the MongoDB server source.

Diagnostic Steps

Related Issues