When building the replica set for MongoDB (version 3.2.9), use Rs.status () to view the state of the replica set and find a member exception: Replica set IDs do not match, details are:
"lastHeartbeatMessage" : "replica set IDs do not match, ours: xxx; remote node‘s: yyy",
"stateStr" : "(not reachable/healthy)"
A variety of methods have been tried, and the member cannot be removed from the primary node, the replica set ID of the member cannot be synchronized by restarting the member's Mongod and forcing Primay to reconfigure.
The last trick, will kill the technology, the data file of the MongoDB instance all deleted, and then in the replica set primary node, re-add the member, and finally the replica set to build successfully.
In MongoDB, the configuration information of replica set is stored in the System.replset collection of the local database, MongoDB cannot synchronize replica set ID, which is very tangled.
MongoDB replica set IDs do not match