Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.7, 4.0.1, 4.1.2
Affects Version/s: 3.6.2, 3.6.5
Component/s: Storage
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.0, v3.6
Sprint:
Storage NYC 2018-07-16, Storage NYC 2018-07-30
Case:
Confidence Status:
None
Work Order:
3

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

We have seen a couple of cases in the field where under heavy cache pressure a node can get stuck with the WT cache full. In the cases seen so far the cache pressure has been due to replica set lag, which causes the majority commit point to lag, creating cache pressure.

So far we don't have a reproducer and don't have FTDC data covering the inception of the issue (~~SERVER-32876~~) so this ticket for now is a placeholder to gather information.

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

metrics.2018-05-30T17-31-46Z-00000
59 kB
May 30 2018 08:32:51 PM UTC
repro-10MBx2.sh
1 kB
May 30 2018 08:29:45 PM UTC
stacks.txt
65 kB
May 30 2018 08:29:45 PM UTC
stuck.png
166 kB
May 30 2018 08:29:45 PM UTC

depends on

SERVER-32876 Don't stall ftdc due to WT cache full

Closed

WT-4105 Optimize cache usage for update workload with history pinned

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-34942 Stuck with cache full during oplog replay in initial sync

Closed

SERVER-36495 Cache pressure issues during recovery oplog application

Closed

SERVER-36496 Cache pressure issues during oplog replay in initial sync

Closed

related to

SERVER-37849 Poor replication performance and cache-full hang on secondary due to pinned content

Backlog

SERVER-35103 Checkpoint creates unevictable clean content

Closed

SERVER-36221 [3.6] Performance regression on small updates to large documents

Closed

SERVER-36238 replica set startup fails in wt_cache_full.js, initial_sync_wt_cache_full.js, recovery_wt_cache_full.js when journaling is disabled

Closed

SERVER-36373 create test to fill WT cache during steady state replication

Closed

WT-4106 Optimize lookaside implementation to the point where I/O can be saturated

Closed

WT-4107 Reduce lookaside usage in update heavy workloads where history is pinned

Closed

mentioned in: Page Loading...

(2 is related to, 7 related to, 1 mentioned in)

Assignee:: Benety Goh
Reporter:: Bruce Lucas (Inactive)
Participants:: Alexander Gorrod, Benety Goh, Bruce Lucas, Githook User, Michael Cahill
Votes:: 1 Vote for this issue
Watchers:: 21 Start watching this issue

Created:: Feb 08 2018 03:54:49 PM UTC
Updated:: Oct 29 2023 10:34:59 PM UTC
Resolved:: Jul 27 2018 02:49:49 PM UTC
Confidence Status Last Update:: 11/Jul/18 4:23 PM

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates