IR WIKI

Load Balancing

3 min read

Overview

This guide explains how to configure Load Balancing for Integriti controllers in a multi-server environment. When multiple installations of Integriti services are deployed, Load Balancing automatically redistributes controllers across Controller Server nodes to evenly distribute load based on the current connection count.

Load Balancing ignores a controller’s configured primary server and moves it to the best available Controller Server. The controller’s configuration is not modified — if the connection to the load-balanced server is lost, the controller defaults back to its primary server.

Prerequisites

  • Integriti High Availability configured with a minimum of two nodes.
  • Integriti Version: V25.1 or higher.
  • Server Nodes (High Availability / Load Spreading) License (part no. 996965).
  • All controllers running V25.1 or higher firmware.

Upgrading from an older version: The default Tolerance is set to 0 (disabled) after upgrade. You must manually configure it once controller firmware has been updated.

Step-by-Step

Step 1: Verify High Availability Setup

  1. Confirm Integriti High Availability is configured with at least two Controller Server nodes.
  2. Refer to Integriti High Availability for full HA setup instructions.

Step 2: Configure Load Balance Tolerance

  1. In Integriti System Designer, navigate to:

    Main Menu → System Settings → General Settings

  2. Locate the Controller Server Load Balance Tolerance property:

    • This value determines the difference in controller count between servers before load balancing triggers.
    • Example: If Tolerance = 10, Node A has 10 controllers connected, and an 11th controller attempts to connect to Node A — that 11th controller is moved to Node B.
    • Set to 0 to disable Load Balancing globally.
    • Default value: 10.

  3. Set the desired tolerance value and save.

Step 3: Configure Per-Controller Exclusion (Optional)

  1. Navigate to the controller you want to exclude:

    Controllers → Double-click controller → Editor Window

  2. Under Connection Details → Connectivity, locate the Excluded From Load Balancing property:

    • False (default): Controller participates in load balancing — the software may move it between servers based on tolerance.
    • True: Controller is excluded from load balancing and always stays on its primary server.

  3. Set as desired and save the controller configuration.

How Load Balancing Works

  • Load balancing triggers when the difference in connected controller counts between Controller Servers exceeds the configured Tolerance.
  • The controller’s primary server configuration is not changed — it serves only as the fallback if the load-balanced connection is lost.
  • Load balancing is enabled by default for fresh V25.1+ installations (Tolerance = 10).
  • For upgrades from older versions, Tolerance defaults to 0 (disabled) and must be manually set.

Verification

  • Connect controllers to the system and verify they appear online.
  • Check the distribution of controllers across Controller Server nodes.
  • If the tolerance value is exceeded, verify that controllers are moved automatically.
  • Test failover: if a load-balanced connection is lost, verify the controller falls back to its primary server.

Troubleshooting

ProblemResolution
Load balancing not occurringVerify Tolerance is set to a non-zero value under System Settings → General Settings. Ensure all controllers are on V25.1+ firmware.
Specific controller should not be movedSet Excluded From Load Balancing = True on that controller’s Connection Details.
Controllers not connecting after upgradeCheck that controller firmware has been updated to V25.1+. If Tolerance is 0, load balancing is disabled but controllers should still connect to primary servers.
Uneven distributionAdjust the Tolerance value — lower values trigger more frequent rebalancing.

Graph View

Backlinks