Cluster/Node Status

This page displays the current state of the cluster.

Cluster/Node status

Nodes have the following possible statuses:

Status Family	Status	Description
Initializing process	Waiting for initial configuration	node waits until the primary-node address is set
	Starting	node handles bootstrap activities
	Waiting for initialization	node waits for the cluster manager (the primary master) to order to transition to INITIALIZE state
	Initializing	node starts services required to be able to connect to other nodes
	Connecting to other nodes	node connects to all other nodes
	Loading warehouse	node loads files from the warehouse (metadata on schemas and tables and indexes)
	Ready to migrate warehouse	node waits for the cluster manager to order to transition to MIGRATE state
	Migrating warehouse	node migrates the warehouse if a migration process is required after an upgrade
	Ready to serve	node waits for the cluster manager to order the transition to SERVE state
Serving	Serving	node is open and allowed to answer incoming queries
On error	On error	node is in error and won't accept incoming queries

An initializing cluster will display the status of each connected node:

A cluster in error will provide an error message describing the problem:

Indexima cluster is available for SQL queries when all nodes are in status "Serving":

Note that only at startup, only the recently used indexes are loaded into memory. Unused indexes won't be loaded to nodes until they are first used. See parameter table.prefetch.lastdays in galactica.conf.

Re-initialize cluster

The button RE-INITIALIZE CLUSTER interrupts nodes communication:
- All running queries are killed
- The nodes move to the initializing status
- The warehouse is not reloaded if the cluster topology hasn't changed
Select the option "Reload Warehouse" to force the cluster to perform a full reload of the tables and indexes from the warehouse.