SQL Error  [V1001]: [Vertica]VJDBC ERROR: NetworkSend on v_node0001: failed to open connection to node v_st_node0001 (socket error: Connection timed out)
The usual reason is that the client is unable to connect to the named node.
Is there any firewall rule blocking connection to TCP port 5433?
Is v_node0001 up? Newer driver versions allow to specify a list of backup nodes to try if the selected node can't connect.
how can we check firewall rule
yes all nodes are up both cluster .
Check with network administrator. On cloud installed clusters, the network security group should allow TCP port 5433 from your IP address.
If possible, connect to the node via SSH to verify connections with local vsql client.
the copy commands or export commands where I can run them in the source cluster or target cluster .
any difference in running that commands in different nodes or clusters
COPY and EXPORT can be run on any node using any SQL client. The nodes need to be able to access the data location for read (COPY) or write (EXPORT). Since COPY reads data and EXPORT writes data, just be sure you run the expected command to read or write on each cluster. For example, to copy data, EXPORT from source cluster and COPY to target cluster using the same shared data location.
Iam Facing this issue everytime i try to execute copy command
ERROR 4054: [cer] NetworkSend on v_node0001: failed to open connection to node v_stab_node0001 (socket error: Connection timed out)
Is this COPY running local, or using shared storage like S3 or NFS, or using a remote connection like ODBC or CONNECT TO VERTICA? It looks like one cluster is unable to connect to a node in another cluster so it would help to understand full setup. If this is using CONNECT TO VERTICA to move data, it is necessary to open a firewall rule for TCP ports 5433 and TCP 5434 between the clusters.
network team saying ports are open and listening too but still getting same error but when i executed copy or export command no data movements found in firewall any other way to resolve this issue .
@puneeth11 Did you just open the ports or is entire subnet open for network communication across the 2 clusters?
Hi @SruthiA just ports are opened how to open subnets and need to make any changes in network interface changes because niode address and export are different in our cluster ..
I'm still not sure we have all details needed to determine where the issue is.
How do you connect to cluster A and cluster B to run SQL? What address is used - node address or export address?
If cluster A and cluster B are not in same subnet or same VPC on AWS, it's likely you'll need to use a public IP address. This is likely the address used to connect directly to cluster A or cluster B. The same address that is used for direct connect from desktop or client, try this address for CONNECT TO VERTICA.
If possible, connect to a node in cluster A, then try to connect to cluster B using "vsql -h "
@puneeth11 : Did you create network interface before setting export address for the node? could you please check with below link?
Hi Sruthi and Bryan
Thanks for ur valuable response finally i completed export from one cluster to another .