1.7. High Availability

When you deploy multiple JBoss Fuse instances in a single OpenShift Enterprise domain, the first application that you create acts as the master node of the cluster. Each subsequent application that you create acts as a slave node.

To prevent the master and slave applications from deploying on the same OpenShift Enterprise node, you must assign different a different gear profile to each set of nodes on which you deploy the JBoss Fuse applications.

The gear profile properties do not need to be unique. You can assign the same gear profile to multiple master nodes or multiple slave nodes.

JBoss Fuse supports management of multiple applications in an ensemble. However, when you deploy the JBoss Fuse applications in OpenShift Enterprise, the ZooKeeper server runs inside the master application. Therefore, you cannot create ensembles of multiple applications.

To manage multiple applications in an ensemble, you must deploy a standalone JBoss Fuse application and create an external ZooKeeper ensemble to manage the JBoss Fuse instances that run in the OpenShift Enterprise domain.

OpenShift Enterprise supports auto-scaling of applications based on HTTP traffic. However, the JBoss Fuse cartridge does not use HTTP to process data. Therefore, you cannot configure auto-scaling for the JBoss Fuse cartridge.