Quantcast
Channel: StackExchange Replication Questions
Viewing all articles
Browse latest Browse all 17268

SECONDARY member of mongodb replica set is not match with PRIMARY

$
0
0

I'm using a mongodb replica set with two nodes in different data centers.

One day, because of unknown packet drop, replica set was broken.

So I restored the replica set by removing/adding secondary node, but there is still something wrong.

Here is the status of the nodes, from the information given by rs.status() and rs.conf():

rs.status() output

rs.conf() output

Why last heart beat is too old?

Replication with two mongodb is not working

For example, the number of documents in the collection 'letter' is not the same across the two nodes:

9873 letter documents in one node9906 letter documents in the other node


Viewing all articles
Browse latest Browse all 17268

Trending Articles