[SERVER-9658] Reduce frequency of debug message "we think data is in ram" Created: 13/May/13 Updated: 11/Jul/16 Resolved: 14/May/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 2.4.3 |
| Fix Version/s: | 2.4.4, 2.5.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Tad Marshall | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows debug build |
||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | Windows | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Debug builds of mongod check to see if our internal working set tracking is accurate, and display the message "warning: we think data is in ram but system says no" when our tracking code thinks that data is in RAM but the operating system's authoritative answer is that the data is not in RAM. We use 'QueryWorkingSetEx()' on Windows and 'mincore()' on other OSes to see if a particular page is in RAM. On Windows, the QueryWorkingSetEx API doesn't actually tell us what is in RAM; it tells us what is in RAM and on the "Working Set" list. Pages that are in RAM and are on the 'Standby' list are not reported by this API. The result is that Windows debug builds spew large quantities of these messages, making logs hard to use. These events should be displayed less frequently. |
| Comments |
| Comment by auto [ 17/May/13 ] |
|
Author: {u'date': u'2013-05-14T14:54:54Z', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}Message: |
| Comment by auto [ 14/May/13 ] |
|
Author: {u'date': u'2013-05-14T14:54:54Z', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}Message: |