One Vertica node in a 3 node cluster is in a constant "recovering" state when trying to start the database.
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
Release: IMDAGG99000-2.8-Infrastructure Management-Data Aggregator
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.
/opt/vertica/bin/vsql -U <dbAdminUser> -w <dbAdminPassword>
vsql> select make_ahm_now(true);
Then restart the database on the problem node.
this sets the Ancient History Mark (AHM) in the database causing the node to rebuild from the other 2 instead of trying to recover from transaction history.