Hi,
With regard to "Native Connection Load Balancing" there are two options:
1. ROUNDROBIN: Chooses the next host from a circular list of currently up hosts in the database (i.e. node #1, node #2, node #3, etc. until it wraps back to node #1 again). Each host in the cluster maintains its own pointer to the next host in the circular list, rather than there being a single cluster-wide state.
2. RANDOM: Chooses a host at random from the list of currently up hosts in the cluster
Does anyone have a recommendation on which is better? I'm guessing ROUNDROBIN.
Native Connection Load Balancing: ROUNDROBIN or RANDOM?
Moderator: NorbertKrupa
-
- GURU
- Posts: 527
- Joined: Tue Oct 22, 2013 9:36 pm
- Location: Chicago, IL
- Contact:
Re: Native Connection Load Balancing: ROUNDROBIN or RANDOM?
It doesn't really matter. Statistically speaking, both options should be equal.
Checkout vertica.tips for more Vertica resources.
Re: Native Connection Load Balancing: ROUNDROBIN or RANDOM?
Does the Management console use the roundrobin capability? It seems to be always running against the first node in the cluster from what I am seeing in query_requests. And the MC constantly runs a select 1 to check jdbc driver connectivity: Did I misconfigure something in MC?
Thanks,
Bryan
Code: Select all
select 1 /*jdbc Connection.isValid() check*/
Thanks,
Bryan
- JimKnicely
- Site Admin
- Posts: 1825
- Joined: Sat Jan 21, 2012 4:58 am
- Contact:
Re: Native Connection Load Balancing: ROUNDROBIN or RANDOM?
Hi,
What version are you running? The 7.1.2-1 hot fix that addressed the excessive connections by MC:
Version: 7.1.2-1
Issue: VER-39069
Component: UI - Management Console
Description: Management Console previously performed continuous license audits, which could negatively affect performance of other queries. This issue has been resolved.
Hopefully that'll help you.
What version are you running? The 7.1.2-1 hot fix that addressed the excessive connections by MC:
Version: 7.1.2-1
Issue: VER-39069
Component: UI - Management Console
Description: Management Console previously performed continuous license audits, which could negatively affect performance of other queries. This issue has been resolved.
Hopefully that'll help you.
Jim Knicely
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.