-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2019-04-08
Currently, when we modify GlobalLockAcquisitionTracker:_globalLockMode, there is a possibility that the step down thread is reading its value concurrently. In order to avoid the step down thread from reading a garbage/stale value, make GlobalLockAcquisitionTracker:_globalLockMode as an AtomicWord<unsigned char>.
- related to
-
SERVER-40069 GlobalLockAcquisitionTracker::getGlobalWriteLocked should return true if the OperationContext it decorates ever held a global write lock
- Closed