[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: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2019-06-17 | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| 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: |
| 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. |