[SERVER-14547] sharding health check for config server Created: 14/Jul/14  Updated: 14/Jul/14  Resolved: 14/Jul/14

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

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

Participants:

 Description   

Hi team,
in mongodb sharding we have either 1 or 3 config server , if any one down all write load goes to first shard correct ? during that period no chunk migration is going on.

lets my one config server down and somehow I am unable to check my shard health then all chunk is written on first shard that is bad .
is there is any such function available to identify config server health or availability.



 Comments   
Comment by Stennie Steneker (Inactive) [ 14/Jul/14 ]

Hi Rajnish,

You should always deploy exactly three config servers for production deployments.

The config servers use a two-phase commit to ensure consistency. If there are differences in essential metadata between config servers (or one or two config servers are unavailable), the cluster's metadata will become read only until the problem is remedied. For more information please see Config Server Availability in the MongoDB manual.

Please also 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-users group (http://groups.google.com/group/mongodb-user) or Stack Overflow with the mongodb tag.

Thanks,
Stephen

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