[SERVER-22975]  Error initializing sharding system: ConfigServersInconsistent hash Created: 05/Mar/16  Updated: 06/Mar/16  Resolved: 06/Mar/16

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

Type: Question Priority: Minor - P4
Reporter: Anand Mohan Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

HI ,

Am Getting the below error when am trying to run mongos .

Error initializing sharding system: ConfigServersInconsistent hash from hostname:26050: { chunks: "595144e50641168dac85217d2781e587", collections: "165eba5d6707780e689bab76ed7150c9", databases: "7e6b8e9a02ed4400e9e00a0054f7e06d", shards: "64671656d53abcca5e982f9b26e14672", version: "e8b7a28e57e92ef98006fc2cb6c13880" } vs hash from D-113043018:26051: { chunks: "d41d8cd98f00b204e9800998ecf8427e", shards: "64671656d53abcca5e982f9b26e14672", version: "e8b7a28e57e92ef98006fc2cb6c13880" }



 Comments   
Comment by Ramon Fernandez Marina [ 06/Mar/16 ]

gg.anands@gmail.com, it appears that you config servers are not in sync, and you'll need to fix that manually.

MongoDB 3.2 introduces Config Servers as Replica Sets, that prevents this scenario. You can upgrade with downtime via this procedure. To upgrade without downtime you'll need to use version 3.2.4, scheduled for release next week (you can download the 3.2.4-rc0 release candidate today, which will provide seamless upgrade to 3.2.4). For the upgrade process to work you must get your config servers in sync first though.

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. See also our Technical Support page for additional support resources.

Regards,
Ramón.

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