[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: |
|
||||||||||||||||||||||||||||||||||||||||
| 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
|
| 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: |
| Comment by Githook User [ 16/Apr/16 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@mongodb.com'}Message: |
| 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 " This reverts commit 5ee7b56b5b625dc62ef80ce4f5742ab837097567. |
| Comment by Githook User [ 08/Apr/16 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@mongodb.com'}Message: |
| 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: |