Mongo Version: 3.6

Database Engine: Wiredtiger

Old Cluster:

  • 1 Primary

  • 1 Secondary

  • 1 Arbiter

We wanted to replace the secondary with a new machine, so we added a new Replica set. Due to which the percentage of Dirty Cache started increasing.

We did not find anything in the Logs. Can anyone help us figuring out what we did wrong.

  • 1
    What do you mean by "we added a new Replica set"? I would add the new node to the replica set, wait for synchronization and then remove the old member. NB, MongoDB version 3.6 is End-Of-Life since April 2021 Feb 14 at 19:03
  • We added a new member (node) to the existing Replicaset. We did the synchronisation from existing secondary and not from primary directly.
    – Bidyut
    Feb 15 at 4:57


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Browse other questions tagged or ask your own question.