Try Starburst Enterprise with Tarball #

You can install Starburst Enterprise platform (SEP) on any 64-bit Linux distribution with the tarball.

Perform the following steps:

  1. Obtain the most recent SEP tar.gz archive
  2. Unpack the archive as root
  3. Add configuration files
  4. Start the SEP server
  5. Obtain the Trino CLI client and run tests

If you are managing clusters on a bare-metal server or virtual machine, consider installing SEP with Starburst Admin.

Prerequisites #

Starburst Enterprise requires a Linux distribution that:

  • Is no more than a few years old
  • Runs on 64-bit Intel hardware
  • Has Python 2.7 or later, needed to run the launcher utility.
  • Has 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.

SEP also installs for evaluation purposes only on a macOS release with the same prerequisites.

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.

This opens a dialog that prompts for your name, email address, and location. 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 buttons.

From the Step 1: Starburst Enterprise section, click the Tarball button. This starts the download of a file named with the pattern starburst-enterprise-*.tar.gz. If prompted to open or save the file, save it to your /home/<username>/Downloads directory.

Next, from the Step 2: Client applications section, click the CLI button. This starts the download of trino-cli-*-.executable.jar; if prompted, save it to your /home/<username>/Downloads directory for later use.

Unpack the archive #

The contents of the tar.gz archive are by default owned by root and include a top-level container directory. The --strip 1 option in the tar command shown here strips that container directory off.

First create an empty target directory, then extract the contents of the tar.gz file without its container directory into the target directory. For example:

cd /home/<username>/Downloads
sudo mkdir -p /opt/starburst
sudo tar xvzf ./starburst-enterprise-*.tar.gz --strip 1 -C /opt/starburst

You can replace the asterisk (*) in the file name with the version of SEP that you downloaded, such as 356-e.1. The command works as shown, without the version string.

The directory /opt/starburst is called the installation directory. Inspect the new directory to find that it contains two top-level files and four directories:

NOTICE
README.txt
bin
lib
plugin
starburst-insights

Add configuration files #

Even small a SEP server must have a minimum set of configuration files before it can start. To add those files, create a directory in /opt/starburst named etc, parallel to bin and lib. Populate etc with the following configuration files, using contents suggested in Configuring Trino.

node.properties
Follow the sample in Node properties. For the node.properties line, the suggested value production has no special meaning; use any value, such as test.
jvm.config
Follow the sample in JVM config. Make sure you are viewing the deployment page that matches the SEP version you downloaded, then use the suggested text verbatim. An exception is to adjust the -XmX value as appropriate for your test environment.
config.properties
Follow the sample in Config properties. Use the third example in that section to specify a combined coordinator and worker machine.
catalog property files
Create a subdirectory etc/catalog. In the catalog subdirectory, create the following files, each containing a single line of text. See Catalog properties for guidance.
File name Contents
blackhole.properties connector.name=blackhole
jmx.properties connector.name=jmx
memory.properties connector.name=memory
tcpds.properties connector.name=tcpds
tpch.properties connector.name=tpch

Start on Configure and define catalogs to learn more about the relationship between data sources, catalogs, and connectors.

Alternate configuration files #

Another way to get started quickly is to use the set of configuration files provided as examples for the O’Reilly book Trino: The Definitive Guide.

To use these ready-to-use configuration files, download the samples from their GitHub location either as a zip file or a Git clone. Let’s say you place your clone or unzip directory in /home/<username>/bookfiles.

From bookfiles, copy the entire etc directory from the single-installation sample folder to your installation directory. For example:

cd /home/<username>/bookfiles/single-installation
sudo rsync -av etc /opt/starburst/

Start the server #

Once configuration files are in place, start the server. From the installation directory, run the following command:

sudo bin/launcher start

For a successful server start, the launcher script returns a process ID. Check the server’s status to make sure the server finished its startup process:

sudo bin/launcher status

As an alternative, look for the exact phrase “SERVER STARTED” in the server.log file, which by default is in the var/log subdirectory of the installation directory:

grep "SERVER STARTED" <installation>/var/log/server.log

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 the Trino CLI as described in CLI.