Contents:
Software setup
Steps:
Before you upgrade:
Inform users of the planned outage for the upgrade.
Please verify that all jobs have completed and that none is pending.
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.
Shut down all Alteryx services:
sudo service trifacta stop sudo killall -u trifacta
Untar the Dependencies folder. Command:
tar -xvf trifacta_<x.y>_deps_<os_version>.tar
where:
<x.y>
is the major-minor release version.
<os_version>
is the operating system version.
Move the
local.repo
file. Command:mv local.repo /etc/yum.repos.d/
Move the
trifacta/rpms
folder into/var/local/trifacta/
. Overwrite the existing rpms folder. Command:cp -rf trifacta/rpms/ /var/local/trifacta/
Clear the yum cache. Command:
yum clean all
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 Alteryx software
Do not uninstall the database.
Upgrade:
NOTE: During the upgrade, you should use the
upgrade
directive for Yum. Avoid using theremove
andinstall
directives, which require manual migration of your saved configuration afterward. Please verify that you have backed up your pre-release configuration files before proceeding.Without Internet access: If the Alteryx node does not have Internet access, you must install using the local dependencies.
Instead of using the
install
directive for Yum, you must use theupgrade
directive.For more information, see Install Dependencies without Internet Access in the Install Guide.
When finished, please return to the next step in these instructions.
For CentOS/RHEL: Upgrade the package with yum, using root. Please execute the following commands:
sudo yum upgrade trifacta
For Ubuntu: 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
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 Alteryx install directory and sub-directories must be owned by the same user that is used to run the Designer Cloud Powered by Trifacta platform. Mismatches in ownership and execution permissions can cause services to fail to start.
Steps:
Before you upgrade, please complete the following:
- Login to the Alteryx node as the root user.
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 Alteryx 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.