[SERVER-5084] Receive uncaught exception error every first statement, error goes away second time Created: 24/Feb/12  Updated: 09/May/12  Resolved: 09/May/12

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

Type: Bug Priority: Major - P3
Reporter: Theo Assignee: Unassigned
Resolution: Done Votes: 1
Labels: crash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RHEL5
MongoD 2.0.0
MongoS 2.0.0 and 2.0.2 both fails


Operating System: Linux
Participants:

 Description   

//first attempt fails all the time

mongos> show collections
Fri Feb 24 13:59:08 uncaught exception: error: {
"$err" : "could not initialize sharding on connection replicaset_2/node01:27017,node02:27017,node3:27017 :: caused by :: specified a different configdb!",
"code" : 15907
}

//second attempt succeed

mongos> show collections
system.indexes
system.users

Config servers are in sync!



 Comments   
Comment by Carlos Moro [ 09/May/12 ]

Please disregard my previous comment.
Error was naive: shard configuration with addshard command was made to config port instead of shard port. Using proper port does not reproduce error.

Comment by Ian Whalen (Inactive) [ 09/Apr/12 ]

@theo, can you confirm if all mongos are being started with the same arguments?

Comment by Eliot Horowitz (Inactive) [ 25/Feb/12 ]

Are all mongos started with the same arguments?

Generated at Thu Feb 08 03:07:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.