Loading...

XML

Word

Printable

JSON

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

duplicates

SERVER-34941 Add testing to cover cases where timestamps cause cache pressure

is related to

SERVER-34938 Secondary slowdown or hang due to content pinned in cache by single oplog batch

SERVER-34941 Add testing to cover cases where timestamps cause cache pressure

SERVER-36495 Cache pressure issues during recovery oplog application

related to

SERVER-36879 write regression test for stuck cache issue during rollback

(1 related to)

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Bruce Lucas (Inactive)
Participants:: [DO NOT USE] Backlog - Replication Team, Bruce Lucas, Ian Whalen, Lingzhi Deng, Spencer Brody
Votes:: 0 Vote for this issue
Watchers:: 15 Start watching this issue