Answers

• DaveT Vertica Employee Employee

  March 2019

  You also need to either set the export_subnet for the database or the export_address for each node and it needs to be a public address the client can reach. Otherwise the load balancer will return a node's private addresses that is used for Vertica node intra-communication. The client will try to connect to that private address and it will be unable to do so.

  Note that 9.2 also has added the ability to use load balancing policies if you want to take a look at that.

  Link that describes requirement for classic load balancing requirements (look at the "Requirements" section):
  https://www.vertica.com/docs/9.2.x/HTML/Content/Authoring/AdministratorsGuide/ManagingClientConnections/LoadBalancing/Legacy/LegacyClusterLoadBalancing.htm

  More info on setting database export_subnet or nodes export_address:
  https://www.vertica.com/docs/9.2.x/HTML/Content/Authoring/AdministratorsGuide/CopyExportData/ChangingNodeExportAddress.htm

  More info on load balancing policies, new in 9.2:
  https://www.vertica.com/docs/9.2.x/HTML/Content/Authoring/AdministratorsGuide/ManagingClientConnections/LoadBalancing/AboutConnectionLoadBalancingPolicies.htm

  0
• mpedroso ✭

  March 2019

  Hey DaveT
  
  Thanks for the answer. I understand, I actually did a cluster installation using the old ips of exclusive communication between the nodes in the vertica_install script parameters ...
  
  Can you change this IP so that Vertica's load balancing uses public IP?
  
  PS. : I have not read the documentation yet, I'll do it now.

  0