Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Won't Do
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Sprint:
Storage - Ra 2020-09-21
Story Points:
3

During recovery, if the history store file doesn't exist treat as a recovery failure and it treats as a PANIC error. Due to the PANIC error, during connection close, the memory that is allocated for pages in the cache are leaked.

Instead of treating the history store file doesn't exist as a recovery error, just verify the history store file before the recovery starts would be good to fix the memory leak.

causes

SERVER-53949 wt_repair_missing_files causes leak error on function make_unique for ASAN for feature flags enabled

Closed

is duplicated by

WT-7451 Memory leak in WT

Closed

WT-11074 Memory leaks in detected mongodb test jstests/disk/wt_repair_missing_files.js

Closed

is related to

SERVER-77680 Disable disk_wiredtiger suite on ASAN again

Closed

WT-4459 Some recovery errors lead to memory leak

Closed

related to

SERVER-51804 MongoDB should restart when WiredTiger detects corruption

Backlog

WT-11074 Memory leaks in detected mongodb test jstests/disk/wt_repair_missing_files.js

Closed

WT-6766 test_wt4156_metadata_salvage: block checksum mismatch

Closed

(3 related to)

Assignee:: [DO NOT USE] Backlog - Storage Engines Team
Reporter:: Haribabu Kommi
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Sep 16 2020 08:12:09 AM UTC
Updated:: Jul 02 2025 02:16:05 PM UTC
Resolved:: Feb 23 2021 02:07:57 AM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates