Release 5.1
Page tree


Support | Blog | Contact Us 

Versions Compared

Old Version 2

changes.mady.by.user docuser1

Saved on

compared with

New Version Current

changes.mady.by.user docuser1

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DEV and version next

D toc

D s install marketplace

This guide steps through the requirements and process for upgrading 

D s product
productee
rtrue
 through the AWS Marketplace. 

Info

NOTE: For upgrading the product, the new instance must be installed directly through EC2. You cannot install the new version using the CloudFormation template, which overwrites your security roles and policies.

These instructions apply only to

D s product
productee
rtrue
 with optional integration with EMR, available the AWS Marketplace. For upgrades of
D s product
productedge
that was installed from the AWS Marketplace, see Upgrade for AWS Marketplace.

Otherwise, please contact your

D s item
itemrepresentative
for upgrade instructions.

Upgrade Path

This upgrade process supports upgrade for the following versions:

Source VersionTarget Upgrade Version

D s product
productee
5.0.x

D s product
productee
5.1.x

Warning

If you are upgrading from a version that is earlier than the supported Source Version listed above for this upgrade process, please use the links below to acquire the AMI(s) and documentation to upgrade to the earliest supported Source Version. Then, return to these instructions to complete the upgrade to this version.

Your VersionTarget VersionAMIDocumentation

D s product
productee
4.2.x

D s product
productee
5.0.x

Please see the AWS Marketplace listing for the product. The AMI is accessible from there.Trifacta Install Guide for AWS Marketplace with EMR v5.0

EMR Upgrade

Before you begin, you should verify that your current EMR cluster version and configuration is supported after the upgrade. If it is not, you must plan to upgrade your EMR cluster after you have upgraded the

D s platform
.

Tip

Tip: For Release 5.1, EMR 5.15.0 and Spark 2.3.0 are recommended.

For more information, see Configure for EMR.

 

Back up data from Marketplace instance

Before you begin, you should back up your current Marketplace instance.

  1. SSH to your current Marketplace instance. For more information, see Install from AWS Marketplace with EMR.

  2. Change to the root user:

    Code Block
    sudo su

  3. Stop the 

    D s platform
     on your current Marketplace instance:

    Code Block
    service trifacta stop
  4. Update the backup script with the most recent version:

    1. Download the backup script from the following location:

      Code Block
      https://raw.githubusercontent.com/trifacta/trifacta-utils/release/5.0/trifacta-backup-config-and-db.sh

    2. Example command to download the script:

      Code Block
      curl --output trifacta-backup-config-and-db.sh https://raw.githubusercontent.com/trifacta/trifacta-utils/release/5.0/trifacta-backup-config-and-db.sh

    3. Overwrite the existing script with the new script you just downloaded:

      Code Block
      mv trifacta-backup-config-and-db.sh /opt/trifacta/bin/setup-utils/trifacta-backup-config-and-db.sh

    4. Update the ownership and permissions of this script:

      Code Block
      chown trifacta:trifacta /opt/trifacta/bin/setup-utils/trifacta-backup-config-and-db.sh
chmod 775 /opt/trifacta/bin/setup-utils/trifacta-backup-config-and-db.sh

  5. Run the backup script:

    Code Block
    /opt/trifacta/bin/setup-utils/trifacta-backup-config-and-db.sh

     

    1. When the script is complete, the output identifies the location of the backup. Example:

      Code Block
      /opt/trifacta-backups/trifacta-backup-5.0+126.20171217124021.a8ed455-20180514213601.tgz

  6. Store the backup in a safe location. If needed, you can store this backup in the S3 bucket used by the platform. Example:

    Code Block
    aws s3 cp /opt/trifacta-backups/trifacta-backup-5.0+126.20171217124021.a8ed455-20180514213601.tgz s3://<my-trifacta-s3-bucket>/trifacta-backups/

Spin up upgraded Marketplace instance and restore data

Now, you spin up the upgraded instance and then restore the data from the pre-upgrade instance into this one.

Info

NOTE: Do not terminate your old instance until your new instance is successfully restored and running properly.

 

Steps:

  1. Spin up the new instance of

    D s product
    productee
    from the AWS Marketplace.

    1. Make sure you use all the same settings as your existing

      D s item
      iteminstance
      (security groups, IAM role, VPC, subnet, etc).

    2. For more information, see Install from AWS Marketplace with EMR.

  2. Verify that the instance has successfully started. If you can connect to the login page, the platform has started.

  3. SSH to the new
    D s item
    iteminstance
    . For more information, see Install from AWS Marketplace with EMR.

  4. Change to root user and change to the root home directory:

    Code Block
    sudo su
cd

  5. Stop the 

    D s platform
     on the instance (should already be stopped):

    Code Block
    service trifacta stop

  6. Download the backup from your storage location and extract its contents. Example:

    Code Block
    mkdir -p /root/trifacta-restore-files
cd /root/trifacta-restore-files
aws s3 cp s3://<my-trifacta-s3-bucket>/trifacta-backups/trifacta-backup-5.0+126.20171217124021.a8ed455-20180514213601.tgz .
tar xzf trifacta-backup-5.0+126.20171217124021.a8ed455-20180514213601.tgz

  7. The backup contents should now be located in a directory with a path similar to the following:

    Code Block
    /root/trifacta-restore-files/trifacta-backup-5.0+126.20171217124021.a8ed455-20180514213601

  8. Execute the restore script. Pass in the path to your unzipped backup as a parameter. Example:

    Code Block
    /opt/trifacta/bin/setup-utils/trifacta-restore-from-backup.sh -r /root/trifacta-restore-files/trifacta-backup-5.1+126.20171217124021.a8ed455-20180514213601

  9. The backup is restored into your new installation.

  10. Users of
    D s product
    productee
    must update the license file (license.json). For more information, see Install from AWS Marketplace with EMR.
  11. After this upgrade is complete, you may upgrade the following:
    1. EMR cluster version to 5.15.0

    2. Spark version to 2.3.0

      Info

      NOTE: The Spark version must be inserted as part of the

      D s platform
      configuration. For more information, see Install from AWS Marketplace with EMR.

Post-upgrade Fixes

Verify migration of EMR settings

If your deployment is integrated with an EMR cluster, after you have completed the upgrade, you may need to manually migrate some EMR cluster settings. Please do the following:

Steps:

  1. Login to the application as an administrator.

  2. In the Admin Settings page, scroll down to the External Service Settings section. Verify that the values in the section are accurate and current.

  3. If the values in the above node look correct, you can stop here. Please proceed to the next section.
  4. If the values are incorrect:
    1. Edit your 
      D s triconf
       backup from the earlier release.

    2. In

      D s triconf
      , locate the values for the parameters in the left column. Insert these parameters in the corresponding setting under External Service Settings on the Admin Settings page of the upgraded instance:

      Info

      NOTE: The AWS EMR Cluster ID should migrate automatically. AWS Region was not tracked via parameter in earlier releases.

      Pre-upgrade

      D s triconf
      setting

      		Post-upgrade External Service setting
      aws.emr.resource.pathResource path
      aws.emr.resource.bucketResource bucket

    3. Save your changes and restart the platform. 

    4. Verify that you have access to EMR cluster resources.

Verify 

The upgrade is complete. To verify:

Steps:

  1. Restart the platform:

    Code Block
    service trifacta start

  2. Run a simple job. It can have a single step in the recipe. 

    Info

    NOTE: Please verify that profiling is enabled. If the job fails with profiling, retry it without profiling, which may assist in troubleshooting any issues.

    Info

    NOTE: This job should be run on all available running environments, including the

    D s server
    and any integrated EMR cluster.

  3. Verify that the job has successfully completed. 
    1. In the Jobs page, locate the job results. See Jobs Page.
    2. Click View Details next to the job to review the profile.

Documentation

You can access complete product documentation online and in PDF format. From within the product, select Help menu > Product Docs.

Noprint

Related Topics

D s also
labelamazon

© 2013-2023 Alteryx® Inc Privacy Policy  |  Terms of Use