top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration

Facebook Login
Site Registration

Can we reduce mongodb failover time? ( currently it takes ~30sec)

+1 vote

We Have a 3 node mongodb setup with a primary,secondary and an arbiter. If a Primary node goes down the election process to choose a new primary is taking around 30 seconds. During this period all the Create and Update operations fail. So is there anyway to reduce this failover time so that the client application can resume normal operations in less time.

What is the ideal way to handle Create and Update failures during the failover time? Should it be queued and retried? if the number of operations are high the queue size will not be enough. So please suggest a solution for this problem.If the failover time can be reduced it would solve this problem.

We tried reducing the heartbeat interval in the replica configuration. It did not help either

posted Aug 14, 2015 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
0 votes

I am running 4 concurrent Requests. Each request is inserting 100000 documents and each document is 5KB size. The database name and collection name are different for each request so that write lock is per Request.

I am running this on MongoDB 3.4 on centos 6.5. I disabled Journal option . The java client that loads data is running bulkwrites with a batch of 1000 documents.

I tried both single server and with 3 shards . With standalone single server, each request completes in around 20-25 secs. With 3 shards configuration, Each request takes around 50 to 60 secs. I wonder why it takes considerable time to insert documents.

+1 vote

Can we implement password complexity in MongoDB?
Like 10 characters long, 1 capital letter, 1 special character etc...

Contact Us
+91 9880187415
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Karnataka INDIA.