BugZero found this defect 16 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
5/3/2024
MongoDB Server
No affected releases provided.
No fixed releases provided.
In WouldChangeOwningShard tests it is possible to have commands fail due to Lock timeout due to a shard version mismatch refresh happening right before the write which prevents us from taking the collection lock in time. See SERVER-61461 and SERVER-67536 for other instances of this failure. We should increase the lock timeout in this test to prevent this from happening