If the PBWM lock is held during the entire background collection validation, then on secondaries it could stall replication, which is undesirable. After opening all of the collection and index cursors, we can release the PBWM lock.
- depends on
-
WT-6503 Cache stuck: eviction couldn't able to progress triggered by number of updates in cache
- Closed
-
WT-6349 Don't truncate history store updates for globally visible timestamped deletes
- Closed
-
WT-6490 Acquire snapshot for eviction threads
- Closed
- is duplicated by
-
SERVER-50398 appliedThrough document write and background validation reads could use the same timestamp
- Closed
-
SERVER-49012 Background validation needs to use ignore_prepare=false
- Closed
-
SERVER-50353 Background validation should periodically restart its storage transaction
- Closed
- is related to
-
SERVER-50398 appliedThrough document write and background validation reads could use the same timestamp
- Closed
-
WT-6767 Adding a new read timestamp config that allows it to be set older than the oldest timestamp
- Closed
- related to
-
SERVER-51302 Override read timestamp check for refreshTransaction
- Closed