[SERVER-23876] Expose WiredTiger cache size in serverStatus Created: 22/Apr/16 Updated: 22/Apr/16 Resolved: 22/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, WiredTiger |
| Affects Version/s: | 3.3.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Kyle Suarez |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Integration 13 (04/22/16) | ||||||||
| Participants: | |||||||||
| Description |
|
The WiredTiger section of serverStatus should also include the wiredTigerCacheSizeGB configuration option. |
| Comments |
| Comment by Kyle Suarez [ 22/Apr/16 ] |
|
The information is already present in serverStatus as db.serverStatus().wiredTiger.cache['maximum bytes configured']. |