Technical troubleshooting and more

when running Vertica vnetperf utility you may face these errors below although you have no FW between servers and the communication is OK and no network errors are observed Vertica DB is up and running on these Vertica hosts as well [Connector Thread 172.16.8.11 ] Couldn't connect to 172.16.8.11 (family 2, attempt 0): Connection refused; errno=111 (Connection refused) [Connector Thread 172.16.8.10 ] Couldn't connect to 172.16.8.10 (family 2, attempt 0): Connection refused; errno=111 (Connection refused) [Connector Thread 172.16.8.12 ] Couldn't connect to 172.16.8.12 (family 2, attempt 0): Connection refused; errno=111 (Connection refused) [Connector Thread 172.16.8.11 ] Could not find anything to connect to for 172.16.8.11; errno=111 (Connection refused) [Connector Thread 172.16.8.10 ] Could not find anything to connect to for 172.16.8.10; errno=111 (Connection refused) [Connector Thread 172.16.8.12 ] Could not find anything to connect to for 172.16.8.12; err...

let's say for example that you have 3 Vertica nodes and the inteconnect communication subnet was 10.0.0.X now for some reason you want to change the internal communication between the nodes to use another interface using this subnet:  192.168.1.X please follow these step by step guide in order to accomplish this target: ----------------------------------------------------------------- first change network from to use point-to-point mode 1. select set_control_mode('pt2pt'); select reload_spread(true); Check in the catalog directory if spread.conf got modified to broadcast mode. 2. Edit admintools.conf  controlmode controlmode = pt2pt 3. Use admintools to distribute database configuration and metadata to all cluster nodes 4. In order to make spread adjust new configuration you need to restart Vertica DB for each Vertica node run these steps to change IP used by interconnect 1. Stop Vertica on node 2.  Change hostname through vsql : alter no...