-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Execution Team 2020-09-21, Execution Team 2020-10-05
-
23
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When a read on a secondary uses kLastApplied/kNoOverlap and encounters a collection catalog conflict, it uses a trick to reacquire the PBWM lock and read without a timestamp.
This was necessary because single-phase background index builds would timestamp writes at future timestamps that may never be seen on secondaries (i.e. "ghost timestamps"). This is not necessary now that simultaneous index builds are the only index builds in 4.5+.
- is depended on by
-
SERVER-38341 Remove Parallel Batch Writer Mutex
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- is related to
-
SERVER-48518 Rollback via refetch (EMRC = false) can make readers to see the rolled back data even after the rollback node catches up to primary.
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-