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.
As part of the design for supporting additional transaction participants we agreed on leaving open transactions that would be reaped eventually. This is currently safe to do since these transactions are essentially read-only and do not affect correctness. However, this means we will unnecessarily hold some locks as part of the transaction that will only be released when we reap the leftover transaction. This also causes artificial delays if we want to perform any resharding/moveChunk operation since those will attempt to acquire with strong locks at one point or another.