At the present time upgrading Continuum is a manual, decision-based process. The upgrade process is quick and painless but does require an outage. This means that you will need to select a period of downtime where pipelines, automation, user logins, etc. may be interrupted. Usually, this period of time is seconds, not minutes. Our goal is to get to a zero-downtime upgrade in the future.
If the Continuum server does not have direct outbound access to the internet you will need to download the file to the Continuum server using an intermediate step such as your desktop, then get the file to the server using sftp or some other protocol.
Step 1. Download the Upgrade File
You may have received an email with a link to download the latest release of Continuum. Use this link in the following command.
curl -O "download link here" Or if you prefer `wget`: wget -O "download link here"
Step 2. Run the Upgrade
Make sure you run the following steps as the Continuum application owner on the Continuum server.
# make the installer executable chmod +x downloadedfile # run the executable, using silent mode (no prompting) ./downloadedfile
The upgrade process performs the following actions:
Stops the Continuum services
Installs the new files into a new directory under $CONTINUUM_HOME (usually under
/opt/continuumunless you have changed the default Continuum installation directories. See Change the Default Installation Directories for more information.)
If you have Continuum installed on a custom location and are now upgrading, the Continuum installer installs Continuum on the same directories where it was installed earlier. Any new paths passed with the installer script during such upgrades are ignored.
Changes a symbolic link /opt/continuum/current to point to the new directory
Performs any database change scripts that may be included
Restarts the Continuum services
At this point you should be able to log back into the Continuum application and its service is returned to normal.
Rolling Back to a Previous Release
If for any reason you need to rollback to a previous release, you can use the following commands to perform the rollback.
First do a directory listing of the Continuum install directory. The following link will list in chronological order from oldest to newest.
ls -ltr /opt/continuum total 12 drwxrwxr-x 3 continuum continuum 4096 Jan 30 11:20 python drwxrwxr-x 9 continuum continuum 4096 Mar 24 13:57 184.108.40.2062 drwxrwxr-x 9 continuum continuum 4096 Apr 3 14:50 220.127.116.114 lrwxrwxrwx 1 continuum continuum 25 Apr 3 14:56 current -> /opt/continuum/18.104.22.1684
You will notice at least one symbolic link named "current" and another actual directory containing the Continuum software. If there has been more than one installation, there will be other directories with a different naming convention for the older installs.
The objective of the rollback will be to stop the Continuum services, change the symbolic link named "current" to point to one of the other Continuum install directories and restart the services.
From the "ls" command output, choose the Continuum install directory to switch to. Then substitute it in the commands below where you see "22.214.171.1242".
ctm-stop-services rm /opt/continuum/current ln -s /opt/continuum/126.96.36.1992 /opt/continuum/current ctm-start-services
Login and check your data.
At this time there is no way to rollback the database version in Continuum. However we make our best effort to make database modification additive so as to not affect previous releases adversely.