web stats
Upgrading Mirth Appliance - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #1  
Old 10-25-2012, 04:49 AM
daigoba66 daigoba66 is offline
Mirth Newb
 
Join Date: Jun 2011
Posts: 6
daigoba66 is on a distinguished road
Default Upgrading Mirth Appliance

We're going to be upgrading our Mirth Appliance cluster (active primary and passive backup setup). We are curious if there is any guidance to upgrading the appliance (and Mirth Connect) in a cluster setup? For instance, should we de-cluster, perform the update and then re-cluster? Or is it simple enough to upgrade the backup, failover and then upgrade the primary?

Ideally we want to keep the cluster available (either Primary or Backup) during the upgrade.
Reply With Quote
  #2  
Old 10-25-2012, 05:13 PM
johnsond johnsond is offline
Mirth Employee
 
Join Date: Jul 2012
Posts: 4
johnsond is on a distinguished road
Default

Hi Daigoba66,

This is a procedure that we use for Mirth Appliance Upgrades on a cluster setup.

1) Stop the clustering service on the primary, and let the backup take over
2) Upgrade the primary
3) Start the cluster on the primary, wait for it to takeover, and then stop the cluster on the backup
4) Upgrade the backup
5) Start the clustering service on the backup
6) Then check both instances to make sure everything is in good working order (all services are running, channels appear normal, etc..

-JDea
Reply With Quote
  #3  
Old 10-25-2012, 07:53 PM
daigoba66 daigoba66 is offline
Mirth Newb
 
Join Date: Jun 2011
Posts: 6
daigoba66 is on a distinguished road
Default

JDea,

Thanks, that is exactly what I was looking for.

--
Joseph Daigle
Reply With Quote
  #4  
Old 10-15-2013, 06:56 AM
hdmoscm hdmoscm is offline
Mirth Newb
 
Join Date: May 2007
Posts: 8
hdmoscm
Default

In reviewing the recommendation outlined in the forum I see a potential for a possible problem. That is: If you have polling channels, (such as a Database Reader, JavaScript Reader, or File Reader on the Primary then when you turn off the clustering service on the primary then both instances of mirth connect will be active and your primary and secondary would both be polling on those channels. This could result in messages getting processed out of sequence. Depending on where these messages are going, this could be a non-issue... or potential problem.

Before the actual update starts, the Upgrade Wizard will automatically scan for unsupported APIs and alert you to any potential problems it finds. (This auto scan is helpful, but should not be considered a full substitution for testing. You should update and test using your Dev and QA instances first.

It is recommended to take a Virtual Machine snapshot using the appropriate features available in your Hypervisor (e.g. VMware ESX or XenServer). This will allow easier rollbacks in case there are unanticipated problems with the updates. This is purely optional, but highly recommended.

Currently we generally recommend to upgrade the secondary appliances first. But this could be considered simply a matter of preference. If you want to test the upgraded (Secondary) appliance before updating the Primary appliance in your cluster, then stop the mirth service on the Primary appliance to allow for testing. Then restart the service on the Primary appliance before updating it to the current revision. (Again, optional.)

You really don't have to stop or start any services, as the systems are designed to upgrade without manual intervention being needed. Of course if you want to test the cluster after both the primary and backup appliances have been updated, then stop the mirth service on the primary and allow the secondary to become the active node. Once you have confirmed that all the channels and features are running properly on the secondary then restart the mirth service on the primary. (Again, totally optional.)
Reply With Quote
Reply

Tags
mirth appliance upgrade

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 02:53 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.
Mirth Corporation