Upgrading an Engine for UNIX Variants

This section covers the guidelines and procedures to follow when upgrading to a new engine version. The steps you follow depend in your requirements for uptime and your tolerance for error.

Additionally, your engine configuration setup will determine which upgrade method will work best. For more information on various configuration scenarios, refer to Engine Configuration Scenarios.

The general process to upgrade an engine is as follows:

  • Obtain the new release zip archive from Transparensee.
  • Uncompress and install it in ~discovery/releases directory following the recommendations in Engine and Data Tool Installation for UNIX Variants.
  • Start the new engine instance using a distinct port from the running engine.
  • Synchronize changesets from the old engine to the new engine.
  • Configure applications to use the new server port
  • Stop the “old” server
  • Update your system init to start the new version when the server starts

The following sections describe general procedures to upgrade individual engine configuration scenarios.

General Upgrade Procedure

The best way to minimize down time is to start the new engine instance alongside the old engine instance, synchronize the changeset data, start using the new server and then stop the old server:

  • Start the new engine instance.
  • Use the new engine instance Admin Tool’s Admin Page to configure the engine to pull changesets and dimensions from the old engine instance.
  • Configure but do not enable any changeset feeds on the new engine instance.
  • When the new engine is fully populated, update your application logic to use the new engine at the new port.
  • Disable changeset processing on the old engine.
  • Stop the old engine
  • Enable changeset feeds on the new engine instance.