Skip to main content

High Availability Configuration Hierarchy

Moogsoft Enterprise deployments use a tiered hierarchy of clusters, groups, instances and roles to achieve High Availability.

A cluster is a collection of Moogsoft Enterprise components that can deliver an uninterrupted processing workflow. To achieve HA you need at least two clusters that include all the Moogsoft Enterprise components. You need an additional, third machine, for message queue and search components.

A group comprises a single component or two identical components that provide resilience over two or more clusters. Moogsoft Enterprise automatically controls the active or passive behaviour and failover of the instances within a group.

An example of a group is a Socket LAM configured for the same source in two separate clusters. Other groups include the following;

  • Servlets for the UI.

  • Moogfarmd for data processing.

  • Individual LAMs for data ingestion. For example the REST LAM.

An instance is an individual component running within a group. Each instance in a group provides resilience for the other instance. For example the primary instance of a Socket LAM pairs with a secondary instance in the second cluster to make a group.

A role within a Moogsoft Enterprise installation is a functional entity containing components that must be installed on the same machine. You can distribute different roles to different machines. For example, the Core role.