Vertica Cluster Node Recovery

During my work with Vertica database, I have encountered some of these scenarios that can be resolved easily if you are able to identify it.

Photo by Markus Spiske on Unsplash

Problem #1:

In a Vertica cluster setup, one or more node is down for a couple of hours and stuck in “DOWN” status (>30 mins) even after a normal start up of the database.

Starting Vertica on all nodes. Please wait, databases with a large catalog may take a while to initialize.
Node Status: v_apddb_node0001: (DOWN) v_apddb_node0002: (DOWN) v_apddb_node0003: (DOWN)
Node Status: v_apddb_node0001: (DOWN) v_apddb_node0002: (DOWN) v_apddb_node0003: (DOWN)
Node Status: v_apddb_node0001: (DOWN) v_apddb_node0002: (DOWN) v_apddb_node0003: (DOWN)
Node Status: v_apddb_node0001: (DOWN) v_apddb_node0002: (DOWN) v_apddb_node0003: (DOWN)
Node Status: v_apddb_node0001: (DOWN) v_apddb_node0002: (DOWN) v_apddb_node0003: (DOWN)
Node Status: v_apddb_node0001: (DOWN) v_apddb_node0002: (DOWN) v_apddb_node0003: (DOWN)
Node Status: v_apddb_node0001: (DOWN) v_apddb_node0002: (DOWN) v_apddb_node0003: (DOWN)
Node Status: v_apddb_node0001: (DOWN) v_apddb_node0002: (DOWN) v_apddb_node0003: (DOWN)
Node Status: v_apddb_node0001: (DOWN) v_apddb_node0002: (UP) v_apddb_node0003: (UP)
Node Status: v_apddb_node0001: (DOWN) v_apddb_node0002: (UP) v_apddb_node0003: (UP)