Details
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?
Attachments
Issue Links
- is documented by
-
DOCS-12799 Docs for SERVER-37761: cacheSizeGB value should have some validation and reporting -- new limit is the WiredTiger maximum of 10TB
-
- Closed
-