[SERVER-4831] Poor error message when trying to add shard with duplicate DB name Created: 31/Jan/12  Updated: 30/Mar/12  Resolved: 02/Feb/12

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

Type: Bug Priority: Minor - P4
Reporter: A. Jesse Jiryu Davis Assignee: A. Jesse Jiryu Davis
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

When running a sharded cluster that contains database 'foo', doing 'addShard' with a server that already contains a database named 'foo', we get an unhelpful error:

"couldn't connect to new shard mongos connectionpool: connect failed repl2/airtop.local:37017 : connect failed to set repl2/airtop.local:37017"



 Comments   
Comment by jitendra [ 28/Feb/12 ]

i got same error

addshard request

{ addshard: "192.168.50.241:25000" }

failed: can't add shard 192.168.50.241:25000 because a local database '00280212' exists in another shard0000:192.168.50.241:10000

Comment by A. Jesse Jiryu Davis [ 02/Feb/12 ]

Sorry Eliot, retesting more carefully I see that the error message is
great: "can't add shard localhost:4007 because a local database 'test'
exists in another shard0:shard0/localhost:4000,localhost:4001"

Please close the ticket

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

Are you sure that was the issue?

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