[SERVER-47774] wiredTigerCacheSizeGB config param accepts 0Gb or any lower value than 0.25gb Created: 24/Apr/20 Updated: 29/Oct/23 Resolved: 08/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Joshua Weinstein | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Minor Change |
| Operating System: | ALL |
| Steps To Reproduce: | Run the command `mongod --wiredTigerCacheSizeGB 0` or any value between 0 and 0.2499 |
| Sprint: | Execution Team 2020-06-15 |
| Participants: |
| Description |
|
The option listed here https://docs.mongodb.com/manual/reference/program/mongod/#cmdoption-mongod-wiredtigercachesizegb does not enforce a lower limit in conjunction with that is documented. You can start mongod with even --wiredTigerCacheSizeGB 0 .
simple fix, PR is already here https://github.com/mongodb/mongo/pull/1359 |
| Comments |
| Comment by Githook User [ 08/Jun/20 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |