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.

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:

  1. Download the most recent SEP RPM package.
  2. Install the package.
  3. Add configuration files.
  4. Start the SEP server with the service script.
  5. Download any supported client tool and query the cluster.

Requirements #

  • 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 service script.
  • Java 11.0.11 or a later Java 11 LTS release from Azul, OpenJDK, or Oracle Java distributions. Newer Java releases may work but are not tested or supported.

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 your /home/<username>/Downloads directory.

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 rpmcommand to install the package:

rpm -i starburst-enterprise-*.rpm --nodeps

Service script #

The RPM installation deploys a service script configured with chkconfig, so SEP starts automatically on OS boot. After installation, you can manage the SEP server with the service command for the starburst service:

service starburst [start|stop|restart|status]
  • start Starts the server as a daemon and returns the process ID.
  • stop Shuts down a server started with either start or run. Sends the SIGTERM signal.
  • restart Stops and then starts a running server, or starts a stopped server, assigning a new process ID.
  • status Prints a status line, either Stopped pid or Running as pid.

Once configuration files are in place, you can run start SEP with following commands:

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 /var/log/starburst/server.log file.

grep "SERVER STARTED" /var/log/starburst/server.log

You can also follow the log with tail:

tail -f  /var/log/starburst/server.log

Installation directory structure #

The RPM package places the various files used by SEP in accordance with the Linux Filesystem Hierarchy Standard. This differs from the default tarball installation of SEP, where all folders are in the installation directory. For example, with a tar.gz file, configuration files are located by default in the etc folder of the installation directory. By contrast, the RPM package installation uses /etc/starburst for the same purpose.

The RPM installation places SEP files using the following directory structure:

  • /usr/lib/starburst/lib/: Various libraries needed to run the product; plugins go in a plugin subdirectory
  • /etc/starburst: General Starburst Enterprise configuration files such as config.properties, jvm.config, and node.properties
  • /etc/starburst/catalog: Connector configuration files
  • /etc/starburst/env.sh: Contains the Java installation path used by Starburst Enterprise, allows configuring process environment variables, including secrets
  • /var/log/starburst: server.log files
  • /var/lib/starburst/data: Data directory
  • /usr/shared/doc/starburst: Documentation
  • /etc/rc.d/init.d/starburst: Service script

RPM-specific configuration settings #

The configuration files need to be placed in the installation directory structure used by the RPM. In addition, the node.properties file needs two properties defined to adjust for the directory structure:

node.data-dir=/var/lib/starburst/data
catalog.config-dir=/etc/starburst/catalog

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 #

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 /var/log/starburst.