Try Starburst Enterprise with RPM #
Users of RedHat Enterprise Linux (RHEL) and CentOS can use the RPM package to install Starburst Enterprise platform (SEP).
The RPM archive includes the application, all plugins, the necessary default configuration files, default setups, and integration with the operating system to start as a service. More details are available in the reference documentation for the RPM archive.
Use Starburst Admin to install and manage a cluster of bare-metal servers or virtual machines. Only use the RPM package to deploy on a single node or a few nodes manually, or if you use an alternative provisioning system. Find more information in our deployment options guide.
You can install and test the RPM with the following steps:
- Download the most recent SEP
- Install the package.
- Optionally update configuration and catalog files.
- Start the SEP server with the service script.
- Download any supported client tool and query the cluster.
- 64-bit versions of RHEL 7, RHEL 8, CentOS 7, or CentOS 8.
- x86-64 hardware.
- Python 2.7 or later, needed to run the
- Java 11.0.11 or a later Java 11 LTS release from Azul, OpenJDK, or Oracle Java distributions as required for your specific SEP version.
Install Java #
Download and install the required Java version for SEP. For example, use the following steps:
- Download Java from Azul:
sudo curl -O https://cdn.azul.com/zulu/bin/zulu11.52.13-ca-jdk11.0.13-linux.x86_64.rpm
- Install Java:
sudo rpm -i zulu11.52.13-ca-jdk11.0.13-linux.x86_64.rpm
- Confirm the required version of Java is available on the path:
Install Python #
Install the Python version for SEP. We recommend using Python 3.x. For example, use the following steps:
- Install Python 3.x:
sudo dnf install -y python3
- To ensure SEP uses Python 3.x upon deployment, you must
sudo update-alternatives --config python
- When prompted, enter the selection number for the version of Python you want
to use. For Python 3.x the path is
- Confirm the required version of Python is available on the path:
Download an SEP archive #
To gain access to SEP archives, existing customers contact Starburst Support. If you are not a customer yet, visit the Starburst website and click either the Get Started or Download Free buttons.
Fill out the form using a valid email address, then click Free Download.
Open your email from Starburst, and click the link to the downloads page.
The Downloads page is organized into a Long-Term Support section at the top with Steps 1 and 2, and a Short-Term Support section at the bottom. Use the LTS option.
From the Step 1: Starburst Enterprise section, click the RPM button.
This starts the download of a file named with the pattern
starburst-enterprise-*.rpm. If prompted to open or save the file, save it to
Install the package #
Copy the RPM to the server, if you have downloaded it on a different machine.
You need root or sudo access to run the installation commands. Use the
rpm command to install the package:
rpm -i starburst-enterprise-*.rpm --nodeps
Service script #
The RPM installation deploys a service script configured with
SEP starts automatically on OS boot. After installation, you can
start the SEP server with the
service command for the
service starburst start
Check the server’s status to make sure the server finished the startup process:
service starburst status
As an alternative, look for the exact phrase
SERVER STARTED in the
grep "SERVER STARTED" /var/log/starburst/server.log
You can also follow the log with
tail -f /var/log/starburst/server.log
The initial install is configured to start up successfully. Modify the configuration files and catalog properties files as desired for your specific scenario. The files are located in standard locations.
Verify the server #
To verify that your locally-run server is operating as expected, invoke the Trino UI as described in Verify the server.
Run queries #
To run queries against your server, use any supported client.
Uninstalling the SEP RPM installation is like uninstalling any other RPM:
rpm -e starburst-enterprise-<version>
After uninstalling, all deployed Starburst Enterprise files are deleted
except for the logs directory
Is the information on this page helpful?