-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
ALL
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.
- related to
-
SERVER-90367 Track the number of times a $lookup appears within a transaction
- Backlog
-
SERVER-90368 Track the number of times a $lookup appears within a transaction and targets a remote shard
- Backlog
-
SERVER-88517 Characterize load that would trigger server failure due to many txns waiting for timeout
- Closed