Installation & Configuration on Kinetica Docs

Adjust Firewall

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

Firewall Settings RHEL 6 RHEL 6 uses iptables by default to configure its firewall settings. These can be updated using the /etc/sysconfig/iptables file, or, if you have X Server running, there is also a GUI for editing the firewall that can be run using the command: system-config-firewall RHEL 7 RHEL 7 continues to use iptables under the hood, but the preferred way to interact with iptables was updated to using the firewall-cmd command or firewall-config GUI.

GPU Driver

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

GPU Driver Matrix Cards Preferred The cards below have been tested in large-scale production environments and provide the best performance for the database. GPU Driver Kinetica Package P4/P40/P100 470.X (or higher) gpudb-cuda-license V100 470.X (or higher) gpudb-cuda-license T4 470.X (or higher) gpudb-cuda-license A10/A40/A100 470.X (or higher) gpudb-cuda-license Supported The cards below are supported for Kinetica but should only be used for smaller, testing workloads or as necessary. GPU Driver Kinetica Package 750ti 470.

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 two methods for installing Kinetica on-premises: KAgent -- The preferred method for installing Kinetica. KAgent automates the installation and configuration of Kinetica, Active Analytics Workbench (AAW) and Kubernetes, rings (High Availability), and more. 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. For offerings provisioned within cloud environments directly, see Cloud-Ready.

KAgent

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

KAgent Installation

KAgent can be deployed as a RHEL or Debian/Ubuntu installation package on any server inside or outside the cluster. After copying the KAgent package to the target server, deploy it using the standard procedures for a local package:

On RHEL:

sudo yum install ./kagent-<version>.<architecture>.rpm

On Debian/Ubuntu:

sudo apt install ./kagent-<version>.<architecture>.deb

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).

Note

If Kinetica is to be installed via KAgent, but managed via command line, the etcd configuration management service will need to be managed separately from the database & system management processes. See Managing Kinetica Services for details.

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 Cards 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.

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 Cards 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 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.1

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.1. Database Clients Database Connectors Database Drivers Core Schemas/Collections Protection SQL Support Schemas/Collections AAW UDF Database Clients The native API is not backward compatible with prior releases; any clients that make use of these interfaces 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.