-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
ALL
-
-
Storage NYC 2018-03-26
This is what happens in the repro. First we open a snapshot cursor on db1.coll. The next operation has a higher txnNumber, so we set _isSnapshotTxn to false. Then we unstash resources from the previous operation onto our OperationContext, since we have not cleared stashed resources. Then at the end of the operation, since _isSnapshotTxn is false, we do not stash resources. This allows us to drop db2.coll.
I did not demonstrate this in the repro, but the second read is also holding the locks from the first read while it is running.
- duplicates
-
SERVER-33432 Implicit transaction abort
- Closed