Load balancing INFINITT PACS

How to load balance INFINITT PACS

The function of the load balancer is to distribute inbound connections across a cluster of INFINITT PACS nodes, to provide a highly available and scalable service. Four virtual services are used to load balance the different aspects of INFINITT PACS.

All VIPs should be configured to use Source IP persistence in order to function correctly. For the INFINITT PACS Web VIP, HTTP Cookie can be used in combination with Source IP. This means, in the event that the HTTP cookie persistence method fails, persistence will fall back to using Source IP.

To provide load balancing for INFINITT PACS, the following VIPs are required:

• INFINITT Web
• DICOM
• QUERY
• MWL

The following table shows the ports that are load balanced:

The INFINITT Web service uses the Negotiate HTTP (HEAD) health check to confirm that both the port and website are running and accessible. The remaining virtual services will use the connect to port health check.

Deployment Concept

Note: It’s highly recommended that you have a working INFINITT PACS environment first before implementing the load balancer.

Note: The load balancer can be deployed as a single unit, although Loadbalancer.org recommends a clustered pair for resilience & high availability. Please refer to section 1 in the appendix of the Deployment Guide for more details on configuring a clustered pair.