-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Query yield call saveLockStateAndUnlock which returns true if locks were released. If locks were released we proceed to check for interrupt and finally abandoning the WT snapshot.
It is not safe to call into the storage engine without a global lock. There could for example be a shutdown in progress that has acquired the global lock in MODE_X and is shutting down the storage engine. If this is the case, we may throw when checking for interrupt which again causes the snapshot do be abandoned when the GlobalLock type is destroyed.
- duplicates
-
-
- Closed
-
- is related to
-
SERVER-88944 Use something better than the GlobalLock to protect storage engine access
-
- Backlog
-
- related to
-
-
- Closed
-
-
-
- Closed
-