[SERVER-2516] mongostat shows incorrect connections number Created: 10/Feb/11 Updated: 30/Mar/12 Resolved: 10/Feb/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 1.6.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Brennan Pang | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS 5.2 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
Running mongostat with no params locally to connect to localhost shows an incorrect number of connections when compared to running with -h hostname or checking the rest interface. -bash-3.2$ ./mongostat -bash-3.2$ ./mongostat -h hostname.com http://hostname.com:28017/serverStatus?text "connections" : { "current" : 208, "available" : 19792 }, |
| Comments |
| Comment by Rostislav Dzinko [ 29/Apr/11 ] |
|
There is one mongo instance running. and see near 50 hanging ('ESTABLISHED') connections. |
| Comment by Eliot Horowitz (Inactive) [ 29/Apr/11 ] |
|
How are you measuring 50? |
| Comment by Rostislav Dzinko [ 29/Apr/11 ] |
|
This bug also affects me. Mongostat shows 500 open connections, when there are really about 50 of those. |
| Comment by Brennan Pang [ 10/Feb/11 ] |
|
Yes it did at the time. Oddly enough, I can't seem to reproduce it from the same machine today. It did seem that the behavior of running ./mongostat without -h was connecting to another one of the set members, which is why the stats looked that way. I'll follow up if I encounter the issue again. |
| Comment by Eliot Horowitz (Inactive) [ 10/Feb/11 ] |
|
Can you verify that hostname.com resolves to the same machine where you did 127.0.0.1? |