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.4
Component/s: Replication
Labels:
- SWKB
- nyc

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

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

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

During recovery oplog application 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

stuck-recovery.png
138 kB
May 18 2018 07:35:35 PM UTC

is duplicated by

SERVER-35191 Stuck with cache full during rollback

Closed

SERVER-35339 Complete recovery failure after unclean shutdown

Closed

is related to

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

Closed

SERVER-36495 Cache pressure issues during recovery oplog application

Closed

related to

SERVER-33191 Cache-full hangs on 3.6

Closed

SERVER-35191 Stuck with cache full during rollback

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-51430 update log message search in recovery_wt_cache_full.js to look at end of oplog application

Closed

(3 related to)

Assignee:: Benety Goh
Reporter:: Bruce Lucas (Inactive)
Participants:: Alexander Gorrod, Benety Goh, Bruce Lucas, Githook User, Gregory McKeon
Votes:: 0 Vote for this issue
Watchers:: 15 Start watching this issue

Created:: May 10 2018 08:30:37 PM UTC
Updated:: Oct 29 2023 10:31:54 PM UTC
Resolved:: Jul 27 2018 02:48:35 PM UTC

Details

Description

Attachments

Attachments

Issue Links

Forms

Activity

People

Dates