[SERVER-16964] Sharded Cluster using Replica set Created: 21/Jan/15  Updated: 21/Jan/15  Resolved: 21/Jan/15

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: 2.4.9
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: vinay.kumar Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Hello,

I've configured a Sharding Cluster with below components.

3 config serves
2 mongos
2 shards (3 replica members each)

Case 1: When 1 out of 3 config server is down. As balancer/split chunks doesn't work all the data is being written to primary shard. Later when the conifg server is back. Data is not being split to other shards.

Is there a way that after config server is back that balancer/split chunks migrate to other shards?

Case 2: As My primary server in mongo is listening to 27011 port. After failover the new primary is 27012. But as the mongos is configured to port 27011. It is failing to connect to shard.

How to configure mongos to use the primary member of replset.?



 Comments   
Comment by Ramon Fernandez Marina [ 21/Jan/15 ]

Thanks for your report vinay.kumar. The SERVER project is for reporting bugs or feature suggestions for the MongoDB server and tools. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group.

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