One Vertica node in a 3 node cluster is in a constant "recovering" state when trying to start the database.
The other two nodes are up but one never completes the recovery cycle and the database never completes it's restart.
When a Vertica node has been down for an extended period of time when you try to bring it up it can get stuck in a "Recovering" state.
Seen often when a node, or all nodes, in a Vertica DB cluster are rebooted without proper database shut down prior to reboot.
All supported Performance Management releases
First on the problem node stop the database then on of the working nodes log into vsql as the dradmin user and set the Ancient History Mark using the procedure below.
This process sets the Ancient History Mark (AHM) in the database causing the node to rebuild from the other 2. This is better and faster than the alternative, allowing it to try recovery from transaction history.