Loading...
Loading...
The Clustering page includes clustering configuration settings that you can modify.
This table contains the configuration settings that appear on the Clustering page, including a description of each element.
| Setting Name | Description | Default Value | Possible Values |
|---|---|---|---|
| Heartbeat Interval | The frequency (in milliseconds) to send heartbeats and channel status updates to the cluster. | 1000 | 200-9999 |
| Heartbeat Timeout | If a node fails to send a heartbeat within the set number of milliseconds, it is considered disconnected from the cluster. | 300000 | 100-9999 |
| Cluster Sync Interval | The frequency (in milliseconds) to query the cluster for new tasks to execute. These tasks handle membership changes, message recovery, role changes, and server name changes. | 1000 | 100-9999 |
| Dashboard Status Sync Interval | The frequency (in milliseconds) to query the cluster to update channel dashboard statuses. | 1000 | 100-9999 |
| Cluster Log Sync Interval | The frequency (in milliseconds) to query the cluster to update alert logs, connection logs, and server logs. | 1000 | 100-9999 |
| Cluster State Sync Interval | The frequency (in milliseconds) to query the cluster to update alert states, connection statuses, and the global map. | 1000 | 100-9999 |
| Lock Poll Interval | (When waiting for another node to finish a particular operation.) The frequency (in milliseconds) to check if the lock on that operation has been released (the lower the value, the higher the load on the database, and the greater the overall performance in Mirth® Connect; the higher the value, the lower the load on the database but the lesser the performance in Mirth® Connect). | 500 | 10-9999 |
| Startup Sync Timeout | The maximum number of milliseconds allowed for a starting-up node to block channel operations in the cluster while the node tries to redeploy channels that changed state during its startup. | 180000 | 20000-999999 |
| Prune Offline Node Interval | Servers that have been offline for longer than the given number of hours will be permanently removed from the cluster's history. | 168 | 1-9999999 |