Add Nodes to an Existing High Availability Installation

Add Composer nodes (or instances) to an existing high availability environment

1. If not already installed, install the Composer instance as though it were a single instance (and not running in a high availability environment). See Install Composer.

2. Edit the zoomdata.properties and query-engine.properties files and ensure that the JDBC settings point to the PostgreSQL data store shared by the entire Composer cluster. Also ensure that the user name and password used to access the PostgreSQL data store are correct in these files. For information about the shared PostgreSQL data store, see Configure a High Availability Environment.

3. Edit the consul.json file on the instance you are adding.

   vi /etc/zoomdata/consul.json

4. Verify the consul.json file looks like this:

   {
   "bind_addr": "0.0.0.0",
   "bootstrap": false,
   "bootstrap_expect": 2,
   "client_addr": "0.0.0.0",
   "data_dir": "/opt/zoomdata/data/consul",
   "server": true
   }

   A bind address (bind_addr) and client address (client_addr) of 0.0.0.0 allow the Consul to listen over all network interfaces. Depending on your network setup, you may want to explicitly specify an IP address for this.

   The bootstrap_expect value is the total number of Composer nodes (instances) in your Composer cluster and must be the same value on every instance in the cluster.

5. Restart all the Composer microservices for the instance. See Restart Microservices.

6. Join each instance to the Consul cluster by running this command:

   /opt/zoomdata/bin/zoomdata-consul join <external-Consul-node-IP>

   You can verify that the node has joined the Consul cluster by running this command:

   /opt/zoomdata/bin/zoomdata-consul members