Configuring a Single Consul Instance
You can configure a single Consul instance to be used by all the nodes in the Composer cluster.
This is not our recommended or preferred method of configuring the Consul in production high availability environments. When a single Consul instance is configured for the entire Composer cluster, it is a single point of failure for the whole cluster. However, this configuration can be used to quickly evaluate Composer high availability clustering feasibility for your site.
Each Consul node can be installed by the Composer Bootstrap installation procedure for a Composer node or using the Consul’s installation guide. By default, the Consul node listens only on the localhost interface (127.0.0.1) and cannot be accessed by external networks. Consequently, it must be reconfigured to allow for incoming client requests.
After the Composer installation is complete, edit the Consul custom configuration file
consul.jsonon each Composer node.
If you did not install the Consul using the Composer Bootstrap installation procedure, its custom configuration file might have a different name and location.
Verify the Consul custom configuration file looks like this:
A bind address (
bind_addr) and client address (
0.0.0.0allow the Consul to listen over all network interfaces. If your network setup has several network interfaces or a docker bridge installed, you may want to explicitly specify an IP address or fully qualified domain name (FQDN) for these. In addition, verify that the host machine's firewall allows for incoming connections to the TCP/8500 port (the default HTTP client port for the Consul node).
bootstrap_expectvalue is the total number of Composer nodes (instances) in your Composer cluster and must be the same value on every Composer instance in the cluster.
Each Composer microservice must be configured with the proper Consul IP address. Add or update the following line in the configuration files for each microservice:
<Consul-host-IP>is the IP address of FQDN of the machine where Consul node is installed and configured. For a complete list of the configuration files for each microservice, see Configuration Property Files. For a list of microservices, see Composer Microservice Name Reference.
Restart all of the Composer microservices for the instance. See Restarting Composer Microservices.