[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 Created: 12/Oct/11 Updated: 11/Jul/16 Resolved: 12/Oct/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | 2.0.2, 2.1.0 |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | John Feibusch | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
We get a lot of messages like this: It looks like this is triggered whenever someone does db.serverStatus(), if virtual - mapped >5000 MB. I would like this to be a configurable value, rather than a fixed size of 5000 MB. Ideally, the threshold could be changed without restarting the server. |
| Comments |
| Comment by auto [ 23/Oct/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: factor number of connections into memory leak warning |
| Comment by Eliot Horowitz (Inactive) [ 12/Oct/11 ] |
|
I think the real problem is the number of connections isn't being factored in. |
| Comment by auto [ 12/Oct/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: factor number of connections into memory leak warning |