About the Cluster Status Tab

This tab lets you monitor the status of each server in the cluster. The Status column displays Stopped, Starting, or Running. A server that is Starting is in the process of initializing the Advanced Clustering plugin and deploying channels into the states in which they currently are deployed on the other servers in the cluster.

A check mark in the Polling and Pruner columns shows which server is designated for those roles. (For details about polling/pruning, see About Polling/Pruning Roles in the About Advanced Clustering Configuration section.)

The Last Joined column indicates when the server last connected to the cluster and began its startup process.

The Last Heartbeat column indicates the last time this server recorded a heartbeat in the shared database. If the server's last-heartbeat time exceeds the heartbeat-timeout period, the server is considered offline by the other servers in the cluster. Should a server stall and fail to send a heartbeat for the timeout length but not actually terminate, this server detects that it failed to heartbeat for the timeout length and shuts down the Mirth Connect process so shared resources are not accessed concurrently.

The IP Address and Port columns indicate the IP address and port on which the server is listening for notifications. These notifications are used to increase performance, especially when the Guarantee Message Order option is being used on any channel. (For details about IP address/port, see About IP Address/Port in the About Advanced Clustering Configuration section.)