Adding Nodes to an Existing High Availability Installation
To add Composer nodes (or instances) to an existing high availability environment:
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 v5.
query-engine.propertiesfiles 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 Deploying Multiple Nodes in a High Availability Installation.
consul.jsonfile on the instance you are adding.
consul.jsonfile looks like this:
A bind address (
bind_addr) and client address (
0.0.0.0allow the Consul to listen over all network interfaces. Depending on your network setup, you may want to explicitly specify an IP address for this.
bootstrap_expectvalue is the total number of Composer nodes (instances) in your Composer cluster and must be the same value on every instance in the cluster.
Restart all of the Composer microservices for the instance. See Restarting Composer Microservices.
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:
Please sign in to leave a comment.