[SERVER-2056] incorrect maxConns Created: 02/Nov/10  Updated: 12/Jul/16  Resolved: 19/Nov/10

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 1.6.3
Fix Version/s: 1.7.4

Type: Bug Priority: Major - P3
Reporter: Joseph Wang Assignee: Unassigned
Resolution: Done Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

linux


Issue Links:
Depends
Operating System: ALL
Participants:

 Description   

That's a bug. Could you open a JIRA?

Alberto.

On Tue, Nov 2, 2010 at 4:43 PM, Joseph Wang <josephykwang@yahoo.com> wrote:

On new server, I see

"connections" :

{ "current" : 3, "available" : 816 }

,

in db.serverStatus() output.

On old server running with --maxConns 5000, I see

"connections" :

{ "current" : 225, "available" : 19775 }

,
Doesn't add up to 5000.

I'm running with mongodb-linux-x86_64-1.6.3.

----- Original Message ----
From: Markus Gattol <markus.gattol@gmail.com>
To: mongodb-user <mongodb-user@googlegroups.com>
Sent: Tue, November 2, 2010 1:20:37 PM
Subject: [mongodb-user] Re: mongod default value for maxConns ?

It's 20,000 as of now
http://www.markus-gattol.name/ws/mongodb.html#server_status --->
connections.available



 Comments   
Comment by auto [ 19/Nov/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: if --maxconns is lower than system can handle, lower limit SERVER-2056
/mongodb/mongo/commit/e23fab42009c21351d97171ff0bec8de15c1bd98

Comment by Robert Fan [ 18/Nov/10 ]

We're seeing this issue as well. Ulimit is at 65k, attempted maxConns in the conf file and the command line - still seeing available 816.

Comment by Alberto Lerner [ 03/Nov/10 ]

maxConns is being overwriteen with 20000 internally. This has to be fixed.

Comment by Joseph Wang [ 02/Nov/10 ]

If --maxConns 5000 is specified, shouldn't current + available connection be 5000. I see 20000.

Comment by Scott Hernandez (Inactive) [ 02/Nov/10 ]

The 819 value seems to be 80% of the ulimit (fd) of 1024. This seems to be an issue with the startup script. Richard knows about it.

Generated at Thu Feb 08 02:58:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.