Managing Kinetica Services

Start Database Services

The following database services can be started via GAdmin or command-line:

• Database
  • httpd
  • Query Service
  • Text Search
• Reveal
• Graph Service

systemctl start gpudb

Stop Database Services

The following database services can be stopped via GAdmin or command-line:

• Reveal
• Graph Service
• Database
  • httpd
  • Query Service
  • Text Search

systemctl stop gpudb

Start System Management Processes

If the cluster was installed via KAgent, the statistics/metrics process, configuration manager, and optional high-availability queues need to be started first.

Run the following as the root user.

1. Start the statistics/metrics manager on the KAgent node (usually head node):

   systemctl start kinetica_stats
   

2. Start the configuration manager, etcd, on every node running it:

   systemctl start kinetica-etcd
   

3. If this is a cluster in a High-Availability ring, start RabbitMQ on every node running it:

   systemctl start gpudb-mq
   

To start all system management processes:

• Host Manager
• GAdmin

Run the following as the root user on every node:

systemctl start gpudb_host_manager

Stop System Management Processes

To stop database services and all system management processes:

• GAdmin
• Host Manager

Run the following as the root user on every node:

systemctl stop gpudb_host_manager

If the cluster was installed via KAgent, the statistics/metrics process, configuration manager, and optional high-availability queues need to be stopped also.

Run the following as the root user.

1. If this is a cluster in a High-Availability ring, stop RabbitMQ on every node running it:

   systemctl stop gpudb-mq
   

2. Stop the configuration manager, etcd, on every node running it:

   systemctl stop kinetica-etcd
   

3. Stop the statistics/metrics manager on the KAgent node (usually head node):

   systemctl stop kinetica_stats
   

Start All Processes

Run the following commands as the root user.

Start the statistics/metrics manager on the KAgent node (usually head node):

systemctl start kinetica_stats

Start the configuration manager, etcd, on every node running it:

systemctl start kinetica-etcd

If this is a cluster in a High-Availability ring, start RabbitMQ on every node running it:

systemctl start gpudb-mq

Start the Host Manager on every node:

systemctl start gpudb_host_manager

Start the database services on the head node:

systemctl start gpudb

Stop All Processes

Run the following commands as the root user.

Stop the database services on the head node:

systemctl stop gpudb

Stop the Host Manager on every node:

systemctl stop gpudb_host_manager

If this is a cluster in a High-Availability ring, stop RabbitMQ on every node running it:

systemctl stop gpudb-mq

Stop the configuration manager, etcd, on every node running it:

systemctl stop kinetica-etcd

Stop the statistics/metrics manager on the KAgent node (usually head node):

systemctl stop kinetica_stats

Processes

To check the status of the database processes:

• Host Manager
• GAdmin
• Stats Services
• Database
  • httpd
  • Query Service
  • Text Search
• Reveal
• Graph Service

Run the following as the root or gpudb user:

service gpudb status

GAdmin

The Kinetica Administration Application (GAdmin) provides a GUI for monitoring various aspects of the system:

• Cluster Health
• Running Jobs
• Information & Diagnostics

API

To determine whether the REST endpoint services are operating, the Python API can be invoked, as follows:

$ /opt/gpudb/bin/gpudb_python /opt/gpudb/kitools/gadmin_sim.py -u <username> -p <password> --table --summary
+-----------------+--------------------------------+----------------------+----------------------+-------+
|     Schema      |           Table/View           |       Records        |       Type ID        |  TTL  |
+=================+================================+======================+======================+=======+
| SYSTEM          | <ALL TABLES/VIEWS>             |                    1 |                      |       |
| SYSTEM          | ITER                           |                    1 |        UNSET_TYPE_ID |    -1 |
+-----------------+--------------------------------+----------------------+----------------------+-------+

+---------------------------+----------------------+
|        Object Type        |        Count         |
+===========================+======================+
| Schemas                   |                    1 |
| Tables & Views            |                    1 |
| Records                   |                    1 |
| Records + Track Elements  |                    1 |
+---------------------------+----------------------+

System

Node

Rank