-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2017-03-06
In bgsync start(), the last applied hash is read from the disk outside mutex, but the last applied optime is read while holding the mutex. We need to make sure they are synced.
The last applied hash is only used for PV0, so this issue will go away when PV0 is deprecated.
- related to
-
SERVER-28272 extend timeout in step_down_during_draining.js when waiting for new primary
- Closed