-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.0.0
-
Component/s: Replication
-
None
-
Replication
-
ALL
These two threads (bgsync+oplogreader/synctail) can both write to the minvalid document.
We should have the helper error if the previous state isn't correct when writing the minvalid document when applying the batch. Then it should take the max of the minvalid.end and min of minvalid.start as the correct minvalid boundaries.
In addition we should change oplogreader.connect to return a status so that bgsync can decide how to enter the too-stale state.
- related to
-
SERVER-21478 Fix lag between updating optime after minvalid leaving node in recovering
- Closed