Hi Kali,
Were you experiencing performance issues on your secondary? Since mongodump is reading every document in your database, that means mongodb must load everything into memory at some point. Increasing resident memory usage can happen as part of normal operation as your system warms up. Are you normally working with only a small subset of documents on your primary?
For your second question, if the secondary goes down and you still have two nodes up, they should have enough votes to reelect the primary even if an election is triggered. Have you made any changes to the number of votes each node has?
Thanks,
~Shaun
On Thursday, October 4, 2012 7:20:07 AM UTC-7, kali wrote:
Hi All,
We are running 3 server replica set(one primary, one secondary and an arbiter) on AWS. Primary & Secondary are EC2 extra large instances and arbiter is a small instance.
Our current server version is 2.0.7 and planning to upgrade to 2.2 soon. We are running with journalling enabled.
We scheduled Mongodump to run periodically on Secondary for daily backups.
I'm little baffled to see the resident memory on the secondary grows continuously whereas primary is almost constant. So what could be the reason behind this behavior? Is Mongodump loads the entire working set into memory during backups?! I also checked and made sure there were no memory leaks(comparing the 2*memory mapped with virtual).
Also, we restarted secondary when it started eating up lot of memory. This eventually caused the primary to step down. Ideally, believing this shouldn't be the behavior?
Thanks in advance.