[SERVER-37761] cacheSizeGB value should have some validation and reporting -- new limit is the WiredTiger maximum of 10TB Created: 26/Oct/18  Updated: 29/Oct/23  Resolved: 12/Jun/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Improvement Priority: Minor - P4
Reporter: Nic Cottrell Assignee: Zach Yam (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-12799 Docs for SERVER-37761: cacheSizeGB va... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-06-17
Participants:
Case:

 Description   

I've seen a situation where the wiredTiger.engineConfig.cacheSizeGB was set to  200453 by mistake. This is equivalent to 200TB. I believe this exceeds the maximum value anyway, but it caused unexpected crashes. 

Can we add a startup warning when this value exceeds the maximum value to try and catch this earlier?



 Comments   
Comment by Githook User [ 12/Jun/19 ]

Author:

{'name': 'Zach Yam', 'email': 'zach.yam@mongodb.com', 'username': 'zachyam'}

Message: SERVER-37761 cacheSizeGB value should have some validation and reporting – new limit is the WiredTiger maximum of 10TB
Branch: master
https://github.com/mongodb/mongo/commit/2cd33c3953e54018d8ed687f6c03c7575fe518eb

Comment by Bruce Lucas (Inactive) [ 26/Oct/18 ]

nicholas.cottrell it may be worth looking at the crashes to see if they reveal missing checks in other places.

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