BugZero found this defect 92 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
3/15/2024
MongoDB Server
No affected releases provided.
No fixed releases provided.
The shard which originally owned the data for the collection namespace in the first incarnation may not be the same shard as the one which own data for the collection namespace in the second incarnation. The lack of an entry in the second shard's config.transactions collection permits the second shard to perform the retryable write for a second time.