[SERVER-23824] mongos couldnt get a connection Created: 20/Apr/16  Updated: 22/Apr/16  Resolved: 22/Apr/16

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

Type: Question Priority: Critical - P2
Reporter: max mustermann Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Hi,

i have mongodb3.2 installed on ubuntu 14.04.

i have:

  • 3 servers with repl set rs0
  • 3 servers with repl set rs2
  • 3 config servers with repl set rs100
  • 1 mongos server

when i start mongos with:

mongos --configdb rs100/hypnos:27019 --keyFile /etc/mongod.key

i get the following error message:

2016-04-20T15:53:20.462+0200 I SHARDING [Balancer] about to log metadata event into actionlog: { _id: "ethon-2016-04-20T15:53:20.462+0200-571789d018093adbc77f39e0", server: "ethon", clientAddr: "", time: new Date(1461160400462), what: "balancer.round", ns: "", details:

{ executionTimeMillis: 30004, errorOccured: true, errmsg: "Couldn't get a connection within the time limit" }

}

can someone tell me what is the problem?

regards, bill



 Comments   
Comment by Ramon Fernandez Marina [ 22/Apr/16 ]

Closing this ticket at your request. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

Comment by max mustermann [ 22/Apr/16 ]

Hi,

you can close this issue. it was because not all mebers could communicate with all memebrs

Comment by max mustermann [ 20/Apr/16 ]

i have to say that this cluster is build completly new and has no databses or collections in it.

Generated at Thu Feb 08 04:04:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.