Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.3.5
Affects Version/s: None
Component/s: Admin, WiredTiger
Labels:
None

Assigned Teams:

Storage Execution
Backwards Compatibility:
Fully Compatible
Confidence Status:
None
Work Order:
0

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

If mongod is run on a machine with a very small amount of memory, for example <1 GB, it still configures a default 1 GB cache. This will almost certainly result in eventual failure of mongod when cache usage approaches the configured maximum and memory is exhausted. We could improve the user experience by either

fail early - refuse to start up in such a configuration
configure WT with a smaller cache by default

depends on

SERVER-23658 Lower default wiredTigerCacheSizeGB to 50% of available memory

Closed

SERVER-23538 should scale TCMalloc cache based on machine size

Closed

is duplicated by

SERVER-27131 While inserting records into MongoDB, the used memory of the instance running MongoDB keeps growing until it is shutdown

Closed

is related to

SERVER-23362 Memory leak symptom in wiredtiger node with 1GB of memory

Closed

related to

SERVER-23624 Allow wiredTigerCacheSizeGB to be specified as a float

Closed

Assignee:: [DO NOT USE] Backlog - Storage Execution Team

Reporter:: Bruce Lucas (Inactive)

Participants:: [DO NOT USE] Backlog - Storage Execution Team, Bruce Lucas, Daniel Pasette, Githook User

Votes:: 0 Vote for this issue

Watchers:: 14 Start watching this issue

Created:: Mar 29 2016 12:44:17 PM UTC

Updated:: Dec 06 2022 04:29:30 AM UTC

Resolved:: Apr 16 2016 02:21:26 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates