Starburst Enterprise
  • Starburst Enterprise overview
  • Data consumers
  • Data engineers
  • Platform administrators
  • Try Starburst Enterprise
    • Resources
  • Starburst Enterprise
  • Marketplace deployments
  • Starburst Galaxy
  • User personas
  • Reference documentation
  • Glossary
  • Knowledge base

    • starburst enterprise > try > Trying Starburst Enterprise on any Linux

    Trying Starburst Enterprise on any Linux #

    You can install Starburst Enterprise platform (SEP) on any 64-bit Linux distribution with 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 Presto CLI client and run tests

    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 (only needed to run the launcher utility)
    • Has Java 11.0.7 or a later Java 11 LTS release from OpenJDK, Oracle, or Azul Java distributions. (Newer Java releases may work but are not tested.)

    (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, visit the Starburst website and click either the Get Started or Start 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.

    A few moments later, you receive email from Starburst with a link to the downloads page.

    The Downloads page is organized into Long-Term and Short-Term Support sections. Choose an LTS edition.

    Download the tar.gz file from the All Platforms LTS link.

    Download the Presto CLI JAR file #

    While you’re on the download page described above, download the Presto CLI client JAR file that matches the version of the server you downloaded. That is, download the file whose name ends with executable.jar. We will take advantage of this file later.

    Unpack the archive #

    The contents of the tar.gz archive are by default owned by root. Select an appropriate location and unpack the files as usual. (This page uses /usr/local as the location.) For example:

    cd /usr/local
sudo tar xvzf ~/Downloads/presto-server-nnn.tar.gz

    where nnn is the version number you downloaded.

    This creates a directory named the same as the basename of the tar.gz file in the current directory, such as starburst-server-nnn. We refer to this as the sep-root directory.

    Your site may have standards for running servers that includes not running as root. If you do not want the SEP server to run as root, create a user named sep and change ownership to sep of all files and directories in the new sep-root directory. Then log in as sep to run the upcoming commands.

    Inspect the new directory to find that it contains three directories:

    bin
lib
plugin

    Add configuration files #

    Even the simplest Starburst Enterprise server must have a minimum set of configuration files before it can start. Create a directory named etc parallel to bin and lib. Populate etc with the following configuration files, using contents suggested on Deploying Presto.

    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. Use the suggested text verbatim, except reduce the -XmX value as appropriate for your test environment.
    config.properties
    Follow the sample in Config properties. Use the third suggestion for a combined coordinator and worker machine.
    catalog.properties
    Follow the sample in Catalog properties. Create a subdirectory catalog under etc. In there, create at least one file for each data source. To start with, create a file named tpch.properties with the following s contents is the single line: connector.name=tpch

    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 Presto: 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 ~/bookfiles.

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

    cd ~/bookfiles/single-installation
sudo rsync -av etc /usr/local/starburst-server-nnn/

    Start the server #

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

    sudo bin/launcher start

    For a successful server start, the launcher script returns a process ID.

    For a sep-root directory in which you changed file and subdirectory ownership, you can drop the sudo or use sudo -U sep to run bin/launcher.

    Verify the server #

    To verify that your locally-run server is operating as expected, invoke the Presto UI as described in Verify the server.

    Run queries #

    To run queries against your server, use the Presto CLI as described in CLI.