The memory leak warning:
warning: virtual size (XXXXXXMB) - mapped size (YYYYYYMB) is large (XXXXXX-YYYYYYMB). could indicate a memory leak
was improved by https://jira.mongodb.org/browse/SERVER-4063 However, some customers are still seeing it occur over and over again in their logs. It has been determined that as long as the difference is not actively increasing, there is no danger. Is it possible for the warning to take into account the growth rate of this difference in addition to the number of connections?
As an alternative, is it possible to reduce the number of times this message is displayed? Presently it is called by mongos and also every time db.serverStatus() is run. Because MMS calls getServerStatus, this can generate a lot of noise in the log files.
- is related to
-
SERVER-4282 clean up log messages
- Closed
-
SERVER-4063 make leak warning take number of connections info consideration WAS: I would like a way to set the threshold for the memory leak warning message
- Closed