Increase in Dirty Cache in Mongodb when we added a new replica set member

Ask Question

Asked 3 months ago

Modified 3 months ago

Viewed 24 times

Mongo Version: 3.6

Database Engine: Wiredtiger

Old Cluster:

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.

asked Feb 13 at 4:21

Bidyut

1011 gold badge1 silver badge3 bronze badges

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
– Wernfried Domscheit
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

Add a comment |

0 Your Answer

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

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.