13388 — StaleConfig
sharding
The shard's cached routing information is stale
What is happening?
StaleConfig (also known as StaleShardVersion) occurs when a shard receives a request with routing metadata that does not match its current chunk ownership. This happens after chunk migrations when the routing tables are being refreshed. Drivers and mongos typically retry transparently.
Common causes
- Chunk migration just completed
- Balancer is actively moving chunks
- mongos routing cache is stale
- Collection dropped and recreated with different shard key