Installation & Configuration on Kinetica Docs

Adjust Firewall

Mon, 01 Jan 0001 00:00:00 +0000

Firewall Settings RHEL RHEL uses the firewall-cmd command or firewall-config GUI for configuring the firewall. For example, the following commands will open up port 8082 publicly: firewall-cmd --zone=public --add-port=8082/tcp --permanent firewall-cmd --reload SUSE SUSE uses the firewall-cmd command or firewall-config GUI for configuring the firewall. For example, the following commands will open up port 8082 publicly: firewall-cmd --zone=public --add-port=8082/tcp --permanent firewall-cmd --reload Ubuntu Ubuntu comes with a ufw (Uncomplicated FireWall) command, which controls the firewall, for example:

GPU Driver

Mon, 01 Jan 0001 00:00:00 +0000

GPU Driver Matrix The cards below have been tested in large-scale production environments and provide the best performance for the database. GPU Driver Kinetica Package T4 525.X (or higher) gpudb-cuda-license V100 525.X (or higher) gpudb-cuda-license A10/A40/A100 525.X (or higher) gpudb-cuda-license L4/L40 525.X (or higher) gpudb-cuda-license H100 525.X (or higher) gpudb-cuda-license

Install Nvidia Drivers on Debian/Ubuntu

Mon, 01 Jan 0001 00:00:00 +0000

This section will provide instructions on installing Nvidia drivers in a Debian/Ubuntu environment, if the target servers have Nvidia GPUs. Ensure the GPUs are Installed Ensure that the lspci command is installed (which lists the PCI devices connected to the server): sudo apt-get -y install pciutils Perform a quick check to determine what Nvidia cards have been installed: lspci | grep VGA The output of the lspci command above should be something similar to:

Install Nvidia Drivers on RHEL

Mon, 01 Jan 0001 00:00:00 +0000

This section will provide instructions on installing Nvidia drivers in an RHEL environment, if the target servers have Nvidia GPUs. Disable Secure Boot and SELinux Note Disabling Secure Boot and SELinux may not be necessary for every setup. The Nvidia drivers are installed by compiling and installing kernel modules. If they are not signed by a trusted source, then you will not be able to use secure boot. Consequently, you will likely want to disable secure boot in the BIOS of your server.

Installation Options

Mon, 01 Jan 0001 00:00:00 +0000

There are three methods for installing Kinetica on self-managed infrastructure: KAgent -- The preferred method for installing Kinetica. KAgent automates the installation and configuration of Kinetica, rings (High Availability), and more. Kubernetes -- Kinetica can be installed to Kubernetes clusters using Helm Charts and the Kinetica Operator for Kubernetes Manual -- Kinetica can be installed manually via command line using common Linux-based package managers. Note Kinetica can be installed on pre-provisioned instances in AWS, Azure, or GCP via KAgent.

KAgent

Mon, 01 Jan 0001 00:00:00 +0000

KAgent Installation

KAgent can be deployed as a RHEL, Ubuntu, or SUSE installation package on any server inside or outside the cluster.

Automatically download & install the latest KAgent version using these commands:

RHEL 8



1
2
3
4


KAGENT_REPO=https://repo.kinetica.com/yum/7.2/CentOS/8/x86_64
KAGENT_PKG=$(wget -q -O - ${KAGENT_REPO} | sed 's/<[^>]*>//g' | grep -o "kagent.*ga.*rpm " | sort -V | tail -1)
wget ${KAGENT_REPO}/${KAGENT_PKG}
sudo yum install ./${KAGENT_PKG}

Ubuntu 20



1
2
3
4


KAGENT_REPO=https://repo.kinetica.com/debian/7.2/Ubuntu/focal/binary-amd64
KAGENT_PKG=$(wget -q -O - ${KAGENT_REPO} | sed 's/<[^>]*>//g' | grep -o "kagent.*ga.*deb " | sort -V | tail -1)
wget ${KAGENT_REPO}/${KAGENT_PKG}
sudo apt install ./${KAGENT_PKG}

Ubuntu 22



1
2
3
4


KAGENT_REPO=https://repo.kinetica.com/debian/7.2/Ubuntu/jammy/binary-amd64
KAGENT_PKG=$(wget -q -O - ${KAGENT_REPO} | sed 's/<[^>]*>//g' | grep -o "kagent.*ga.*deb " | sort -V | tail -1)
wget ${KAGENT_REPO}/${KAGENT_PKG}
sudo apt install ./${KAGENT_PKG}

SUSE 15



1
2
3
4


KAGENT_REPO=https://repo.kinetica.com/yum/7.2/SUSE/15.3/x86_64
KAGENT_PKG=$(wget -q -O - ${KAGENT_REPO} | sed 's/<[^>]*>//g' | grep -o "kagent.*ga.*rpm " | sort -V | tail -1)
wget ${KAGENT_REPO}/${KAGENT_PKG}
sudo zypper install ./${KAGENT_PKG}

Alternatively, visit the KAGENT_REPO link below to search for a specific version of KAgent, change KAGENT_PKG to that version on line 2, and then run the modified commands to download & install that version:

RHEL 8



1
2
3
4


KAGENT_REPO=https://repo.kinetica.com/yum/7.2/CentOS/8/x86_64
KAGENT_PKG=kagent-7.2.0.4.20240326024429.ga-0.x86_64.el8.rpm
wget ${KAGENT_REPO}/${KAGENT_PKG}
sudo yum install ./${KAGENT_PKG}

Ubuntu 20



1
2
3
4


KAGENT_REPO=https://repo.kinetica.com/debian/7.2/Ubuntu/focal/binary-amd64
KAGENT_PKG=kagent_7.2.0.4.20240326024429.ga-0_amd64.ubuntu20.04.deb
wget ${KAGENT_REPO}/${KAGENT_PKG}
sudo apt install ./${KAGENT_PKG}

Ubuntu 22



1
2
3
4


KAGENT_REPO=https://repo.kinetica.com/debian/7.2/Ubuntu/jammy/binary-amd64
KAGENT_PKG=kagent_7.2.0.4.20240326024429.ga-0_amd64.ubuntu22.04.deb
wget ${KAGENT_REPO}/${KAGENT_PKG}
sudo apt install ./${KAGENT_PKG}

SUSE 15



1
2
3
4


KAGENT_REPO=https://repo.kinetica.com/yum/7.2/SUSE/15.3/x86_64
KAGENT_PKG=kagent-7.2.0.4.20240326024429.ga-0.x86_64.sles15.3.rpm
wget ${KAGENT_REPO}/${KAGENT_PKG}
sudo zypper install ./${KAGENT_PKG}

This installs the package to the directory /opt/gpudb/kagent and registers and starts the kagent_ui service. KAgent will open port 8081 on the local firewall (if enabled).

Kinetica Installation with KAgent

Mon, 01 Jan 0001 00:00:00 +0000

Kinetica installation and configuration instructions using KAgent for On-Premise hardware. Note Kinetica can be installed on pre-provisioned instances in AWS, Azure, or GCP via KAgent. For offerings provisioned within cloud environments directly, see Cloud-Ready. System Requirements Certified OS List Minimum Hardware Requirements GPU Driver Matrix Active Directory KAgent Installation Kinetica Installation KAgent UI Cluster Deployment Security Nodes Credentials Installation Validation Curl Test API Test GAdmin Status Test Ingest/Read Test Core Utilities Environment Configuration and Tools Helper Scripts Logging Additional Configuration Uninstallation System Requirements Operating system, hardware, and network requirements to run Kinetica.

Kinetica Installation with Kubernetes

Mon, 01 Jan 0001 00:00:00 +0000

Kinetica installation and configuration instructions for Kubernetes using Helm Charts and the Kinetica Operator for Kubernetes. Note Kinetica can be installed manually on pre-provisioned instances in AWS, Azure, or GCP. For offerings provisioned within cloud environments directly, see Cloud-Ready. System Requirements Limitations Kubernetes Installation System Requirements Kinetica supports Kubernetes versions 1.25 and higher. Kinetica is supported on the following Kubernetes environments: Vanilla Kubernetes Amazon Elastic Kubernetes Service (EKS) Microsoft Azure Kubernetes Service (AKS) Red Hat OpenShift Container Platform kind K3s Limitations The following Kinetica features are not currently supported in Kinetica on Kubernetes:

Manual Kinetica Installation

Mon, 01 Jan 0001 00:00:00 +0000

Kinetica manual installation and configuration instructions. Note Kinetica can be installed manually on pre-provisioned instances in AWS, Azure, or GCP. For offerings provisioned within cloud environments directly, see Cloud-Ready. System Requirements Certified OS List Minimum Hardware Requirements GPU Driver Matrix Cluster Preparation Networking Configuration Default Ports Port Usage Scenarios Firewall Settings System Settings Transparent Huge Pages Active Directory Nvidia Drivers Installation Configuration Initialization Visual Initialization Console Initialization Passwordless SSH Starting Kinetica Validation Curl Test API Test GAdmin Status Test Ingest/Read Test Core Utilities Environment Configuration and Tools Helper Scripts Logging Uninstallation System Requirements Operating system, hardware, and network requirements to run Kinetica.

Migrating To Kinetica 7.2

Mon, 01 Jan 0001 00:00:00 +0000

While any version of Kinetica can be upgraded to the latest version using KAgent, there are several aspects of upgrading that should be considered before doing so, as well as a number of steps that should be taken after installing Kinetica 7.2. Database Clients Database Drivers Core Disk-Optimized Column Attribute Store-Only Column Attribute CONCAT_TRUNCATE() Function HASH() Function AAW Database Clients The native APIs are backward compatible with prior releases; any clients that make use of these interfaces do not need to be updated after installation.

Ports

Mon, 01 Jan 0001 00:00:00 +0000

Default Ports The default ports used for communication with KAgent, Kinetica (and between servers, if operating in a cluster), and various important services follow. The Nodes column will list either Head--that the corresponding port only needs to be opened on the head node, or All--that the corresponding port needs to be opened on the head node & worker nodes. Important While the table below lists KAgent and the graph server as being on the head node, these features could be kept on machines entirely separate from Kinetica if desired.