-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 3.7.4
-
Component/s: Index Maintenance, Storage
-
None
-
Fully Compatible
-
ALL
-
Repl 2018-05-07
-
50
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
During initial sync, a secondary will timestamp an index build at the clusterTime, which may occur after the lastAppliedOpTime. The lastAppliedOpTime is used to indicate the latest a reader is allowed to read. If secondary reads are allowed during batch application, a reader will wait for future catalog changes that may never come. The current workaround is to retry the read while taking the PBWM lock, which is suboptimal.
- is related to
-
SERVER-34440 Secondary reads from internal (non-network) clients should read at the last applied timestamp
-
- Closed
-