Updating Your Matillion HA Cluster

Updating Your Matillion HA Cluster


Overview

This article describes the options available to you when it comes to keeping your Matillion HA cluster’s software up to date on AWS.

We recommend you update Matillion as soon as a new release is available, to take advantage of the latest features and performance enhancements.

There are two ways to update:

  • Create a new cluster and migrate your work
  • In-place update

The preferred, and safest, way to upgrade is option 1: to launch a new Matillion cluster (running the latest version), and use the Migration Tool to copy your work from the old cluster to the new one. This option gives you a simple, low risk backout plan.


When to update

A new version will become available roughly every 8 weeks. As soon as this happens you will see a message in the Notices section at the bottom right of the screen in the main Matillion user interface.


Create a new cluster and migrate your work

With this option, you launch a new HA cluster, using the same settings as your existing one.

We recommend that you create a set of re-runnable scripts which will enable you to automate the build of a new HA cluster. For example using CloudFormation, based on the templates that Matillion make available for download.

Once the new HA cluster has been created:

  • In your network settings, allow the new load balancer to accept incoming connections on ports 80 and 443 from the load balancer of the existing HA cluster.

  • Use the Migration Tool to copy your work

  • Verify that the new server is working correctly

  • Switch off all schedules on the old HA cluster, replacing them with schedules running on the new cluster.

  • Turn off the nodes of the old cluster, keeping them for a defined period of time as a backup


In-place update

Choose a time when schedules are not due to run, and proceed as follows.


Switch off Matillion on all nodes

SSH onto each node in turn and issue this command:

sudo service tomcat8 stop

Confirm that tomcat is actually stopped via the following command. It should return no active processes.

ps -ef | grep java


Take a backup of all nodes

We strongly recommend you complete this step, since this will give you a backout option if you decide to revert to the original configuration for any reason.

Document the current date and time (reference for Point in Time recovery of RDS Postgres instance, if required).

In the EC2 Management Console locate the Instance running Matillion ETL and select it.

Find Root devices and then select the EBS ID of the volume.

Right click on the volume and select Create Snapshot.

Enter a Name and Description for your snapshot, including the name of the server.

Repeat for other EC2 node

In the EC2 dashboard click SNAPSHOTS, and wait for creation to complete on both instances.


Perform the updates

SSH to the first EC2 instance.

Install Matillion updates

sudo yum update matillion-*

Install Linux security updates

sudo yum update --security

Repeat for the second EC2 instance.


Restart Matillion

SSH to the first EC2 instance

sudo service tomcat8 start

Repeat on the second EC2 instance


Testing

Confirm that you can open all the following in a web browser, and that you can log in to Matillion:

  • Address of first server
  • Address of second server
  • Load balancer


Backout of the update

If you decide to revert to the original version the steps are:

  • Re-create both EC2 instances from the snapshots
  • Revert the RDS database to the point-in-time when the backup was taken
  • Restart Matillion on both nodes


Cleanup

Set a calendar reminder to delete the backup snapshots.