RPM package#

Users of RedHat Enterprise Linux 7 or 8 and CentOS 7 or 8 can use the RPM package to install Starburst Enterprise. Other versions or distributions are not supported.

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 deploy and manage a SEP cluster using the RPM package on a bare-metal server or virtual machine infrastructure.

Find more information in our deployment options guide.

Only use the RPM package to deploy on a single node or a few nodes manually, or if you use an alternative provisioning system:

  • Download the RPM installation package as described on the download page.

  • Use the rpm or yum command to install the package:

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

Control script#

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

service starburst [start|stop|restart|status]

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 tar.gz installation of SEP, where all folders are in the installation directory. For example, with the tar.gz, 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 Starburst Enterprise 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 - Log files

  • /var/lib/starburst/data - Data directory

  • /usr/shared/doc/starburst - Docs

  • /etc/rc.d/init.d/starburst - Control script

RPM-specific configuration settings#

In an RPM installation, the node.properties file needs two additional properties, because the directory structure is different from the standard established by the tar.gz installation:

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

Uninstalling#

Uninstalling an RPM installation is like uninstalling any other RPM. Run:

rpm -e starburst-enterprise-<version>

After uninstalling, all deployed Starburst Enterprise files are deleted except for the logs directory /var/log/starburst.