What is the "LoadBalancer" that is mentioned in TIBCO Data Virtualization cs_cluster.log?

What is the "LoadBalancer" that is mentioned in TIBCO Data Virtualization cs_cluster.log?

book

Article ID: KB0075256

calendar_today

Updated On:

Products

TIBCO Data Virtualization

Description

In a TIBCO Data Virtualization (TDV) cluster, it is normally advised (but not required) to implement a request routing load balancer to direct client requests to an appropriate cluster node and evenly distribute user requests across the cluster. That load balancer is not a TDV device, it is provided by your choice of load balancer vendor.


What is the "LoadBalancer" seen mentioned in our cs_cluster.log?  Is it the same thing?
Example entries:
INFO 2019-05-03 16:35:41.878 -0700 LoadBalancerImpl - LoadBalancer added cluster member: <a server id>
INFO 2019-05-03 16:35:41.879 -0700 LoadBalancerImpl - LoadBalancer registered for cluster life cycle events

Issue/Introduction

This concerns the TDV cluster.

Resolution

The "LoadBalancer" you see mentioned in the cs_cluster.log is not the traditional user-request routing load balancer used outside the TDV cluster.  It is the internal TDV coordinator used to manage trigger-based requests
For each internal request (originating from a trigger), the TDV cluster time-keeper will call this internal "LoadBalancer" to decide which of the cluster node members should process the request. This is done when a trigger is configured to fire only once per cluster.

The cluster log's use of the word "LoadBalancer" isn't equivalent to the better known external request router and shouldn't be assumed as one. There is no need for TDV administrators to service or manage the "LoadBalancer" entity mentioned in our cluster log.