Page tree

Outdated release! Latest docs are Release 8.2: Upgrade Software

   

Contents:


Software setup

Tip: Please verify that you have created a valid backup before you begin. The software upgrade may go faster if the logs directory has been backed up and then emptied during the upgrade. For more information, see Backup and Recovery.

Steps:

Before you upgrade:

  1. The following packages have been downloaded to the Trifacta node:

    1. Trifacta software

    2. Hadoop dependencies (if applicable)

    3. trifacta-server-dependencies

    4. These are available from the Trifacta FTP site.

  2. Inform users of the planned outage for the upgrade.
     

  3. Please verify that all jobs have completed and that none is pending.

  4. Release 5.0 and earlier: Check that there are no services issues in the Diagnostics page:

    NOTE: You must be logged in as an admin user.

    http://<hostname>:<port_number>/diagnostics

    This feature is deprecated in Release 5.1 and later.

  5. Shut down all Trifacta services:

    sudo service trifacta stop
    sudo killall -u trifacta 
  6. Untar the Dependencies folder. Command: 

    tar -zxvf trifacta_<x.y>_deps_<os_version>.tar

    where:
    <x.y> is the major-minor release version.
    <os_version> is the operating system version. 
     

  7. Move the local.repo file. Command: 

    mv local.repo /etc/yum.repos.d/
  8. Move the trifacta/rpms folder into /var/local/trifacta/.  Overwrite the existing rpms folder. Command:

    mv -rf trifacta/rpms/ /var/local/trifacta/

Upgrade other components

Depending on your upgrade path, you may be required to upgrade external components. 

  • For more information on supported Hadoop components, see Install Reference in the Install Guide.

Upgrade Trifacta software - CentOS/RHEL

  1. Clear the yum cache. Command:

    yum clean all
  2. Do not uninstall the database.

  3. Upgrade:

    NOTE: During the upgrade, you should use the upgrade directive for Yum. Avoid using the remove and install directives, which require manual migration of your saved configuration afterward. Please verify that you have backed up your pre-release configuration files before proceeding.

    1. Without Internet access: If the Trifacta node does not have Internet access, you must install using the local dependencies. 

      1. Instead of using the install directive for Yum, you must use the upgrade directive. 

      2. For more information, see Install Dependencies without Internet Access in the Install Guide.

      3. When finished, please return to the next step in these instructions.

    2.  Upgrade the package with yum, using root. Please execute the following commands:

      sudo yum upgrade <trifacta_rpm_file>
  4. Since the upgrade process does not modify the databases, the metadata for the older jobs should still persist.

If it is not already in the appropriate directory, move license.json into the deployment. Example:

cp /tmp/license.json /opt/trifacta/license/license.json

See License Key in the Install Guide.

Upgrade Trifacta software - Ubuntu

  1. Do not uninstall the database.

  2. Install dependencies:

    1. The following dependencies are updated for this release. They must be uninstalled before upgrade and then re-installed after upgrade. Please execute the following commands to uninstall the dependencies:

      dpkg --remove nginx
      dpkg --remove nodejs
      dpkg --remove trifacta
    2. Untar the dependencies and install them from the folder. The following is for the Ubuntu 16.04 server dependencies:

      tar -zxvf trifacta-server-deps-7.6.1-ubuntu-16.04.tar.gz
    3. The trifacta-repo is created. Use the following commands to install the appropriate versions of nodeJS and nginx for this release:

      dpkg -i trifacta-repo/nodejs_12.19.1-1nodesource1_amd64.deb
      dpkg -i trifacta-repo/nginx_1.17.7-1~xenial_amd64.deb

      For more information, see System Requirements in the Planning Guide.

  3. Upgrade using apt-get, using root:

    sudo dpkg -i <new-trifacta-binary>.deb

    The above might generate an error, which is ok. Continue:

    sudo apt-get -f -y upgrade
  4. Since the upgrade process does not modify the databases, the metadata for the older jobs should still persist.

If it is not already in the appropriate directory, move license.json into the deployment. Example:

cp /tmp/license.json /opt/trifacta/license/license.json

See License Key in the Install Guide.

Set file ownership

All files in the Trifacta install directory and sub-directories must be owned by the same user that is used to run the Trifacta platform. Mismatches in ownership and execution permissions can cause services to fail to start.

Steps:

Before you upgrade, please complete the following:

  1. Login to the Trifacta node as the root user.
  2. Execute the following command. The user that is being granted ownership of the install directory is trifacta, which is the default user that runs the platform. If you are using a different user to run your Trifacta deployment, please substitute that name.

    chown -R trifacta:trifacta /opt/trifacta

Do not restart the platform yet. Additional configuration is required first.

This page has no comments.