BugZero found this defect 27 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
4/22/2024
MongoDB Server
No affected releases provided.
No fixed releases provided.
A direct connection to a shard could fail with staleConfig after SERVER-80135 since shardCollection information refresh has been converted from sync to async. If a direct connection ends up using stale information, the command fails with the sharding status of collection XYZ Is not currently known and needs to be recovered. The fix is to not use the direct connection, or do something before to force a refresh.