October 20th, Q&A session: Get you issues solved and questions answered!

GitHub logo
Edit

Installing Using DEP and RPM Package

Apache Ignite can be installed from the official RPM or DEB repositories.

Installing Deb Package

Configure the repository:

sudo apt update
sudo apt install dirmngr --no-install-recommends
sudo bash -c 'cat <<EOF > /etc/apt/sources.list.d/ignite.list
deb http://apache.org/dist/ignite/deb/ apache-ignite main
EOF'
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 379CE192D401AB61
sudo apt update

Install the Apache Ignite package:

sudo apt install apache-ignite --no-install-recommends

This will install the following files into your system:

Folder Mapped To Description

/usr/share/apache-ignite

The root of Apache Ignite’s installation

/usr/share/apache-ignite/bin

Bin folder (scripts and executables)

/etc/apache-ignite

/usr/share/apache-ignite/config

Default configuration files

/var/log/apache-ignite

/var/lib/apache-ignite/log

Log directory

/usr/lib/apache-ignite

/usr/share/apache-ignite/libs

Core and optional libraries

/var/lib/apache-ignite

/usr/share/apache-ignite/work

Ignite work directory

/usr/share/doc/apache-ignite

Documentation

/usr/share/license/apache-ignite-2.9.0

Licenses

Running Ignite as a Service

Note
If running on Windows 10 WSL or Docker, you should start Apache Ignite as a stand-alone process (not as a service).

To start an Ignite node with a custom configuration, run the following command:

sudo systemctl start apache-ignite@<config_name>

The <config_name> parameter specifies the path to the configuration file relative to the /etc/apache-ignite folder.

To launch the node at system startup, run the following command:

sudo systemctl enable apache-ignite@<config name>