This guide steps through the requirements and process for upgrading through the AWS Marketplace.
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 with optional integration with EMR, available the AWS Marketplace. For upgrades of that was installed from the AWS Marketplace, see Upgrade for AWS Marketplace.
Otherwise, please contact your for upgrade instructions.
This upgrade process supports upgrade for the following versions:
|Source Version||Target Upgrade Version|
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 Version||Target Version||AMI||Documentation|
|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|
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 .
Tip: For Release 5.1, EMR 5.15.0 and Spark 2.3.0 are recommended.
For more information, see Configure for EMR.
Before you begin, you should back up your current Marketplace instance.
SSH to your current Marketplace instance. For more information, see Install from AWS Marketplace with EMR.
Change to the root user:
Stop the on your current Marketplace instance:
service trifacta stop
Download the backup script from the following location:
Example command to download the script:
curl --output trifacta-backup-config-and-db.sh https://raw.githubusercontent.com/trifacta/trifacta-utils/release/5.0/trifacta-backup-config-and-db.sh
Overwrite the existing script with the new script you just downloaded:
mv trifacta-backup-config-and-db.sh /opt/trifacta/bin/setup-utils/trifacta-backup-config-and-db.sh
Update the ownership and permissions of this script:
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
Run the backup script:
When the script is complete, the output identifies the location of the backup. Example:
Store the backup in a safe location. If needed, you can store this backup in the S3 bucket used by the platform. Example:
aws s3 cp /opt/trifacta-backups/trifacta-backup-5.0+126.20171217124021.a8ed455-20180514213601.tgz s3://<my-trifacta-s3-bucket>/trifacta-backups/
Now, you spin up the upgraded instance and then restore the data from the pre-upgrade instance into this one.
NOTE: Do not terminate your old instance until your new instance is successfully restored and running properly.
Spin up the new instance of from the AWS Marketplace.
Make sure you use all the same settings as your existing (security groups, IAM role, VPC, subnet, etc).
Verify that the instance has successfully started. If you can connect to the login page, the platform has started.
Change to root user and change to the root home directory:
sudo su cd
Stop the on the instance (should already be stopped):
service trifacta stop
Download the backup from your storage location and extract its contents. Example:
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
The backup contents should now be located in a directory with a path similar to the following:
Execute the restore script. Pass in the path to your unzipped backup as a parameter. Example:
/opt/trifacta/bin/setup-utils/trifacta-restore-from-backup.sh -r /root/trifacta-restore-files/trifacta-backup-5.1+126.20171217124021.a8ed455-20180514213601
The backup is restored into your new installation.
license.json). For more information, see Install from AWS Marketplace with EMR.
Spark version to 2.3.0
NOTE: The Spark version must be inserted as part of the configuration. For more information, see Install from AWS Marketplace with EMR.
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:
In the Admin Settings page, scroll down to the External Service Settings section. Verify that the values in the section are accurate and current.
In , 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:
NOTE: The AWS EMR Cluster ID should migrate automatically. AWS Region was not tracked via parameter in earlier releases.
|Post-upgrade External Service setting|
Save your changes and restart the platform.
The upgrade is complete. To verify:
Restart the platform:
service trifacta start
Run a simple job. It can have a single step in the recipe.
NOTE: Please verify that profiling is enabled. If the job fails with profiling, retry it without profiling, which may assist in troubleshooting any issues.
NOTE: This job should be run on all available running environments, including the and any integrated EMR cluster.
You can access complete product documentation online and in PDF format. From within the product, select Help menu > Product Docs.