Node State

Advanced Alerting User Guide

Deployed State

The Deployed State trigger type observes the state of the currently deployed channels. You can use this to alert when a channel has stopped or started for a certain amount of time. For example, in the following image, the alert triggers if the channel is in the Starting, Stopping, or Stopped states for longer than 10 minutes. Image showing an alert that triggers if the channel is in the Starting, Stopping, or Stopped states for longer than 10 minutes. As another example, you can set up an alert to trigger if someone has attempted to stop a channel, but it remains in the Stopping state for some period of time: Image that shows an alert that triggers if someone has attempted to stop a channel, but it remains in the Stopping state for some period of time. Option Description Longer Than This alert triggers after a channel/connector has been in a selected state for longer than this amount of time. If left blank, this alert triggers immediately when a channel/connector enters a selected stat

Advanced Alerting User Guide

About Trigger Types

Trigger types are pre-defined actions that initiate alerts. The following sections describe the different trigger types supported by the Advanced Alerting extension. Channel Error The Channel Error type triggers whenever a channel encounters an error. No. of Messages (Sliding Window) The No. of Messages (Sliding Window) trigger type listens for incrementing statistics on your channel or connector. If a certain amount of increment events occur for a particular statistic in a certain window of elapsed time, the alert triggers. No. of Messages (Threshold) The No. of Messages (Threshold) trigger type observes the current queued or error statistics for a particular channel or connector. If the statistic is greater than equal to the specified threshold for a certain amount of time, this alert will trigger. Deployed State The Deployed State trigger type observes the state of the currently deployed channels. SSL Certificate Validation The SSL Certificate Validation trigger type listens for err

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

Advanced Clustering Troubleshooting

I restarted a node in the cluster and launching the Administrator now hangs on "Loading Extensions". This happens when the node did not shut down gracefully. Shutting down the node gracefully allows it to unregister itself from the cluster. Without unregistering, the cluster will prevent the node from rejoining the cluster for 5 minutes. To prevent this from occurring again, be sure to allow the node to shut down gracefully. The 5-minute wait period can be bypassed by running this query on the cluster's shared database:UPDATE m_cluster_nodes SET session_id = NULL WHERE server_id = 'the server id'

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

Strict Mode Enabled

This option is enabled by default to preserve the behavior of the clustering plugin upon upgrade to 3.12 or later. When this option is enabled, the Advanced Clustering extension ensures that all channel operations (deploy/undeploy/start/stop/etc.) are fully synchronized across the entire cluster, meaning that only one deploy/start/etc operation can be running at any given time. In addition, new servers that start up and attempt to join this cluster will be blocked by the following operations: Other servers starting up / joining the cluster Performing a channel deploy/undeploy/start/stop/pause/resume Performing a connector start/stop task Performing the Remove All Messages task for a channel Performing the Remove Results task for a channel Deleting a channel Performing message recovery for an offline server The clustering plugin does this by having each server obtain two locks as part of the startup process: startupDeploy: This lock prevents other servers from entering the startup proce

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

About Advanced Clustering Configuration

When the Advanced Clustering plugin is installed, the Clustering tab appears on the Settings page in Mirth® Connect. Image of the Clustering tab on the Settings page On this page, you can configure various timing settings used by the Advanced Clustering plugin. The page also features - in the Node Configuration section - a list of servers that have registered with the cluster, including status information about each server. Image of the Node Configuration section on the Clustering tab About Cluster Settings The Clustering page includes clustering configuration settings that you can modify. About Polling and Pruning Roles About Command Center Processor Role This topics helps you understand how to use the Advanced Clustering feature in conjunction with the Command Center Base plug-in. About IP Address and Ports

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

About Polling and Pruning Roles

One requirement of the Advanced Clustering plugin is that all participating servers in the cluster be connected to a single, shared database. Because of this requirement, the plugin needs to enforce that only one server in the cluster is assigned to execute the data pruner on its defined schedule. Likewise, a similar problem exists for channels with polling source connectors (File Reader, Database Reader, JavaScript Reader). Typically, a polling source connector polls a shared file system or an external database, in which case, not all servers in the cluster should perform this operation. If they did, you may end up with the same HL7 message file being processed once for each server in the cluster. To avoid this problem, the Advanced Clustering plugin designates one server in the cluster to perform these polling operations. To designate a particular server as the preferred "polling" or "pruning" server, select the appropriate server by selecting its radio button in the Node Configurati

Node State

Recommendations

Deployed State

About Trigger Types

Advanced Clustering Troubleshooting

Strict Mode Enabled

About Advanced Clustering Configuration

About Polling and Pruning Roles

Node State

Deployed State

About Trigger Types

Advanced Clustering Troubleshooting

Strict Mode Enabled

About Advanced Clustering Configuration

About Polling and Pruning Roles