Configuring failover for RabbitMQ - Genetec Mission Control™ 2.11 GA

For high availability, you must first configure a RabbitMQ cluster with a master node (primary server) and a secondary node (secondary server). After a working cluster is created, you can mirror the nodes. This ensures that when the master node is unavailable, the secondary node can be reached so no data is lost.

1. Configure a RabbitMQ cluster.
   1. Copy the .erlang.cookie file from the master node to the secondary node.
      This file is located in two places on the master node, it must be copied to the same two locations on the secondary node:

      • C:\Windows\System32\config\systemprofile
      • %HOMEDRIVE%%HOMEPATH%

        Usually C:\Users\<username>

   2. Restart the RabbitMQ service on the secondary node.
   3. On your RabbitMQ master node, open the RabbitMQ Command Prompt and enter:

      C:\Program Files\RabbitMQ Server\rabbitmq_server-<version>\sbin\rabbitmqctl start_app

      Where <version> is the version number of your RabbitMQ installation package.

   4. On the secondary node, open the RabbitMQ Command Prompt and enter:

      C:\Program Files\RabbitMQ Server\rabbitmq_server-<version>\sbin\rabbitmqctl stop_app
      C:\Program Files\RabbitMQ Server\rabbitmq_server-<version>\sbin\rabbitmqctl join_cluster rabbit@<MasterNodeName>
      C:\Program Files\RabbitMQ Server\rabbitmq_server-<version>\sbin\rabbitmqctl start_app

      NOTE: <MasterNodeName> is case sensitive.
      This adds the secondary node to a cluster with the master node.
2. Mirror the RabbitMQ master and secondary node.
   On either the master or secondary node, open the RabbitMQ Command Prompt and enter:

   C:\Program Files\RabbitMQ Server\rabbitmq_server-<version>\sbin\rabbitmqctl set_policy ha-all "" "{""ha-mode"":""all""}"