Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Gone away
Priority: Major - P3
Fix Version/s: None
Affects Version/s: 3.6.4
Component/s: Replication, WiredTiger
Labels:
None

Assigned Teams:

Replication
Operating System:
ALL
Sprint:
Storage NYC 2018-09-10
Confidence Status:
None
Work Order:
0

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

FTDC.png
214 kB
Sep 03 2018 03:35:24 AM UTC

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

(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

Created:: May 23 2018 03:40:22 PM UTC

Updated:: Oct 27 2023 08:43:25 PM UTC

Resolved:: Oct 02 2023 06:27:12 PM UTC

Confidence Status Last Update:: 28/Aug/18 1:47 PM