Fail Over Replica Set Mongodb

[Alexander Orwell Wolf]

Hello,

I have a replicaset with 3 nodes;

Server 1:

• primary node

Server 2:

• Secondary node
• Arbiter node

when I stopped server 2 with secondary and arbiter, my primary in server 1 change to secondary.

What can I do to have primary node at server 1 if server 2 is offline?

Regards!

[SHAILESH PURANI]

You can set the priority and accordingly it will works.

Regards,

[Jeff Sherard]

Alexsander,

By necessity - Server 1/primary node will become a secondary if Server 2 goes down.  There is no longer a 'majority' available in the replica set (2/3).

You can force reconfigure the replica set to drop Server 2/secondary and Server 2/arbiter from the rs.config().  Essentially creating a 1 node replica set.

https://docs.mongodb.org/manual/tutorial/reconfigure-replica-set-with-unavailable-members/

As per the documentation:

"Use this procedure only to recover from catastrophic interruptions."

The two server architecture you have is described is fine for a test environment.  But you would never want to run that way in a production environment.  Three servers would be a much better configuration.  You can make the server for the arbiter much much smaller since it is not a data bearing node.

Cheers,

Jeff Sherard

MongoDB Master