MongoDB Shard Configuration Server not synchronizing causes the MONGOs process to start failing

Production environment, the use of MongoDB shards, due to sudden power outages, the service up again when the discovery of three MONGOs process has a boot failure, multiple attempts still cannot start. View the log with the following contents:

650) this.width=650; "title=" MongoDB Shard Configuration Server Out-of-sync causes MONGOs process start failure-an_world-wind drizzle "src=" http://img0.ph.126.net/ Otqoyicsygsolfxtw4dseg==/6630386068491511482.jpg "style=" border:0px; "/>

It probably means that the configuration server Configserver data is out of sync.

Workaround:

1. Kill all MONGOs processes

2. Connect to the Configserver of each shard, Run command Db.runcommand (' Dbhash ')

3. The MD5 value is found, when the two MD5 values are the same, and the non-functioning MD5 and the above are not the same

4. Delete the dbpath that are not functioning properly, and copy the data from the DBPath to the normal operation.

5. Restart all MONGOs processes and find everything OK

At this point, the problem is resolved satisfactorily.

This article is from the "Black Time" blog, so be sure to keep this source http://blacktime.blog.51cto.com/11722918/1795309

MongoDB Shard Configuration Server not synchronizing causes the MONGOs process to start failing