Deadline Install on a Failover Cluster

Just wanted to know how I can install the database and the repository on a failover cluster.
We have two file servers and a single storage box. Right now they are set up as active/passive, so once one fails or disconnects the other takes on the role of a file server.

In the Deadline installation documents it says you can specify two or more database servers and there is an option for a Replica Set. This seems like the option I can use but I’m not really sure how to set that up. If anyone has set that up before please let me know.

Hello,

The simplest instructions on how to set up Mongo Replica Sets is found at docs.mongodb.com/manual/tutoria … plica-set/ but let us know if you run into issues.

I went through the tutorial in the link.
That seem to have worked but I had to create two new databases on each server as the default deadline databases could not be overwritten.
I’m not really sure how to configure deadline to use the two file servers and the new replica set.

Edit:
I configured the config.conf on each of the file servers to include the replica set name, and it looks like the databases are syncing, except now I need both file servers to be up for the repository to have a connection. If one goes down, there is no connection. So this is opposite of what I want.

Hello,

For the repository side of things, you would need to set up a syncing and failover system of your own, as Deadline doesn’t have anything built in for this. The replica set should not need both machines to be up, but they should remain up 24/7 in case of failure.

Hi,
for the repository side we have it setup on the failover cluster share. So if one file server goes down the share gets automatically remapped to the file server that is still up.
I was able to solve my previous database problem, you actually need 3 db servers to be up for the replica set to properly failover. What I have a problem with is how can I set up the connections.ini file to function when one of the file servers fails.
For example I have 2 file servers and 1 arbiter machine (which doesn’t host any db but instead only elects which server becomes the primary db server).
fileServerA:27080
fileServerB:27017
arbServer:27018

In connections.ini I can specify multiple IPs for multiple servers but only one port, the Alternate Port option doesn’t seem to work. So when when fileServerA goes down there is no connection to the mongo db because the ports are different.

Hello,

The best advice I can give is to change the port on the 2 alternate machines so that they are the same as the primary, as you are right, the ini file can only contain one port number. You don’t necessarily need to reinstall, instead you can stop the MongoDB, then go to “[DB]\mongo\data\config.conf” and change the port in the file. If you do this for your two alternates, then restart their Mongo services, this should bring them back into sync.