Mule runtime clusters versus server groups
How an on-premises Mule 4 cluster shares state through its memory grid, runs primary-only sources and hands work between nodes, and how that differs from a server group. Also covers store profiles, node prerequisites and the two ways to manage a cluster.
Analyze the mode of operation of a Mule runtime cluster that differentiates it from other deployment options.
~8 min read · 9 practice questions
What the exam expects
- Explain the active-active mode of an on-premises Mule runtime cluster and what the primary node does differently.
- Distinguish a cluster, which shares state, from a server group, whose application instances run in isolation.
- Design flows so later processing stages can move to another node, and recognize where cluster coordination stops.
- Choose between the performance and reliable store profiles for a container or a single application.
- Prepare nodes for a cluster: version alignment, discovery settings, ports and a single management method.
Cluster: Mule runtime engines acting as one virtual server over a shared memory grid. Server group: servers used as one deployment target whose instances run in isolation. Primary node: the node that runs schedulers and primary-only sources. Store profile: the setting that decides whether queues and object stores are distributed and backed up (HA cluster overview).
Sources for this section (1)
Key facts
- Detail
- Active-active; all nodes process messages
- Detail
- Object stores, VM queues and the LockFactory are replicated
- Detail
- Application instances run in isolation
- Detail
- Runs only on the primary polling node
- Detail
- Runs on the node where the event began
- Detail
- Applies only to nodes inside the cluster
- Detail
- Application-level store profile overrides the container
- Detail
- Same Mule (and cumulative patch), agent and Java
- Detail
mule.cluster.nodesplusmule.cluster.multicastenabled=false
- Detail
- Manual files are not synced; platform changes override them
- Detail
- Up to eight servers
- Detail
- TCP 5701, 5702, 5703
- Why can't the servers in a unicast Runtime Manager cluster take DHCP-assigned addresses?
- When a cluster is configured through Runtime Manager on its default ports, which TCP ports must stay open between nodes?
- Which discovery type lets a server be configured as a node before it is Running?
- Why does an on-premises cluster still need a load balancer or client-side failover for HTTP traffic?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Integration Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 40 lessons of the MuleSoft Platform Integration Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both