How to monitor the status of the Vertica database upon restart

Products

• CA Infrastructure Management
• CA Performance Management - Usage and Administration
• DX NetOps

Issue/Introduction

After restarting the Vertica database, how can the progress of startup be monitored to verify when its status is up?

 

Environment

Release: 20.2, 21.2, 22.2
Component: Data Repository

Resolution

There are 2 options you could use to monitor/check the status of the database when restarting it.

1. /opt/vertica/bin/adminTools -t view_cluster -h

Usage: view_cluster [options]

Options:

-h, --help show this help message and exit
-x, --xpand show the full cluster state, node by node
-d DB, --database=DB filter the output for a single database

*Examples run as the DR admin user:

/opt/vertica/bin/adminTools -t view_cluster
DB | Host | State
--------+------+-------
drdata | ALL | UP

/opt/vertica/bin/adminTools -t view_cluster -x
DB | Host | State
--------+----------------+-------
drdata | 10.10.10.1 | UP
drdata | 10.10.10.2 | UP
drdata | 10.10.10.3 | UP

*This also works in single node vertica installations. Example run while starting on a single node system:

/opt/vertica/bin/adminTools -t view_cluster
DB | Host | State
--------+------+--------------
drdata | ALL | INITIALIZING

2. ./vsql -U <user> -w <password> -c "select * from nodes;"

Example output:

node_name |node_id | node_state | node_address | node_address_family | export_address | export_address_family | catalog_path | node_type | is_ephemeral | standing_in_for | node_down_since

-------------------+-------------------+------------+---------------+---------------------+----------------+-----------------------+---------------------------------------------------+-----------+--------------+-----------------+-----------------

v_drdata_node0001 | 45035996273704980 | UP | 10.10.10.10 | | 10.10.10.10 | | /catalog/drdata/v_drdata_node0001_catalog/Catalog | PERMANENT | f | |

(1 row)

 

Additional Information

It can be useful to monitor the status of the Vertica database upon startup in order to determine when the database is fully initialized and ready to accept connection from the Data Aggregator system. If you try to restart/start the Data Aggregator before the Data Repository's Vertica database is fully initialized, the Data Aggregator services will not startup or may start but shortly after, shut down due to not being able to communicate with the Vertica database on the Data Repository.