-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.6.4
-
Component/s: Replication, WiredTiger
-
None
-
Replication
-
ALL
-
Storage NYC 2018-09-10
During rollback we don't advance the oldest timestamp. This can pin a lot of data in the cache and we can get stuck with the cache full.
- depends on
-
WT-4144 Fix rollback_to_stable with lookaside history
- Closed
- duplicates
-
SERVER-34941 Add testing to cover cases where timestamps cause cache pressure
- Closed
- is related to
-
SERVER-34938 Secondary slowdown or hang due to content pinned in cache by single oplog batch
- Closed
-
SERVER-34941 Add testing to cover cases where timestamps cause cache pressure
- Closed
-
SERVER-36495 Cache pressure issues during recovery oplog application
- Closed
- related to
-
SERVER-36879 write regression test for stuck cache issue during rollback
- Closed