[SERVER-23391] Improve behavior when running under WiredTiger on machines with little memory Created: 29/Mar/16  Updated: 06/Dec/22  Resolved: 16/Apr/16

Status: Closed
Project: Core Server
Component/s: Admin, WiredTiger
Affects Version/s: None
Fix Version/s: 3.3.5

Type: Improvement Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-23658 Lower default wiredTigerCacheSizeGB t... Closed
depends on SERVER-23538 should scale TCMalloc cache based on ... Closed
Documented
is documented by DOCS-7669 wiredTigerCacheSizeGB, inMemorySizeGB... Closed
Duplicate
is duplicated by SERVER-27131 While inserting records into MongoDB,... Closed
Related
related to SERVER-23624 Allow wiredTigerCacheSizeGB to be spe... Closed
is related to SERVER-23362 Memory leak symptom in wiredtiger nod... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Participants:

 Description   

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


 Comments   
Comment by Githook User [ 16/Apr/16 ]

Author:

{u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@mongodb.com'}

Message: SERVER-23391 Lower WiredTiger cache size floor
Branch: master
https://github.com/mongodb/mongo/commit/9406722720821f7152f44ddcfd12a6447ec58ae4

Comment by Githook User [ 16/Apr/16 ]

Author:

{u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@mongodb.com'}

Message: SERVER-23391 Lower WiredTiger cache size floor
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/b268e0b8bcf8a99dce40bab71077ab355df71227

Comment by Githook User [ 09/Apr/16 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: Revert "SERVER-23391 Lower WiredTiger cache size floor"

This reverts commit 5ee7b56b5b625dc62ef80ce4f5742ab837097567.
Branch: master
https://github.com/mongodb/mongo/commit/c5fcd8a55623a97e34879ec36d47dc1b1d675de5

Comment by Githook User [ 08/Apr/16 ]

Author:

{u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@mongodb.com'}

Message: SERVER-23391 Lower WiredTiger cache size floor
Branch: master
https://github.com/mongodb/mongo/commit/5ee7b56b5b625dc62ef80ce4f5742ab837097567

Comment by Daniel Pasette (Inactive) [ 29/Mar/16 ]

I think our initial assumption that WT needed at least 1GB cache for proper operation was misguided. We can simply remove the 1GB floor here without any risk IMO:
https://github.com/mongodb/mongo/blob/master/src/mongo/db/storage/wiredtiger/wiredtiger_init.cpp#L74-L76

Generated at Thu Feb 08 04:03:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.