The Vertica Database Forums

When trying to remove a host from a running cluster (the node was already removed from the database, it is no longer being used), the script seems to try to update the remaining hosts.

Is this correct? It tries to setup all directories and permissions again, NTP, password, even if Vertica is already installed and running on those hosts.

Which files need to be updated in order to finish the process? It seems to us that the only places where this host is still present is in the AT metadata files (siteinfo.dat), spread configuration file (vspread.conf) and in the monitoring.nodes table

Thanks in advance

Hi!

>>Which files need to be updated in order to finish the process?
All depends on cluster topology - so admintools.conf should be enough, since it contains a cluster topology.
vspread.conf easily can be generated from admintools.conf
siteinfo.dat - irrelevant to subject.

@walito - How many nodes remain in your database? What is your database K-Safety?

The cluster is going to keep running with 3 nodes, and its K-Safety is 1.
We had 5 nodes.
We know that it is not recommended to have a cluster with only 3 nodes, but we need to do it.

Our main concern was that when issuing the script "update_vertica -R hostname", it tries to modify the installation
on the remaining hosts.

Thanks again.

Hi!

What is a question? What do a script?

1. admintools metadata reconfigured
2. spread is reconfigured and reloaded
3. RPM checked (but not installed)
Thats all.

>> It tries to setup all directories and permissions again, NTP, password, even if Vertica is already installed and running on those hosts.
No.

HI!

FIX: /opt/vertica/sbin/cluster_clean_node
its kills all Vertica processes and uninstalls Vertica instance

@walito - You wrote this:

We know that it is not recommended to have a cluster with only 3 nodes, but we need to do it.

Is it true that having only three nodes is not recommended? Where did you read this? We only have three nodes in production. Is that insufficient?