Hello friends! I'm starting my studies with Vertica and I'm trying to install a cluster of the community version to test and study the viability of deployment for my company and I have some doubts. In the community version can I upload a cluster with only two nodes? Or is it obligatory 3 knots? How does vertical load balancing work? Example: In a 3-node cluster, I have 3 distinct IPs for each node. When I connect to the database through a tool like DBeaver, which IP should I use? Is there another IP that manages this?

Question

Vertica Cluster questions

Forum|Forum|8 years ago
September 13, 2018
3 replies
18 views

+1

mpedroso
Participating Frequently

Hello friends!

I'm starting my studies with Vertica and I'm trying to install a cluster of the community version to test and study the viability of deployment for my company and I have some doubts.

In the community version can I upload a cluster with only two nodes? Or is it obligatory 3 knots?
How does vertical load balancing work? Example: In a 3-node cluster, I have 3 distinct IPs for each node. When I connect to the database through a tool like DBeaver, which IP should I use? Is there another IP that manages this?

+2

Jim_Knicely
Participating Frequently
Forum|Forum|8 years ago
September 13, 2018

Hi!

1) Vertica Community Edition licenses include 1 terabyte of data and a limit of 3 nodes. So you can have a cluster of 1-3 nodes, but you need at least 3 nodes for high availability (K-Safety = 1).

See:
https://www.vertica.com/docs/9.1.x/HTML/index.htm#Authoring/AdministratorsGuide/Licensing/AboutVerticaLicenses.htm

https://www.vertica.com/docs/9.1.x/HTML/index.htm#Authoring/ConceptsGuide/Components/K-Safety.htm

2) Native connection load balancing is a feature built into the Vertica Analytic Database server and client libraries as well as vsql. For tools like DBeaver, you can connect to any node (IP). If you want that connection to be load balanced, you have to turn on connection load balancing in the database and set a JDBC connection property called "ConnectionLoadBalance" to True. The node that you connect to will pass off your session to the next node in "round robin" order.

See:
https://www.vertica.com/docs/9.1.x/HTML/index.htm#Authoring/AdministratorsGuide/LoadBalancing/EnablingAndDisablingNativeConnectionLoadBalancing.htm

https://www.vertica.com/docs/9.1.x/HTML/index.htm#Authoring/ConnectingToVertica/ClientJDBC/JDBCConnectionProperties.htm