5. Configure Load Balancer
Starting October 11, 2024 (Zephyr Enterprise 8.2), the Zephyr Enterprise documentation moved from its current location on Atlassian to a dedicated, standalone Zephyr Enterprise documentation page. Please see: https://support.smartbear.com/zephyr-enterprise/docs/en/zephyr-enterprise/zephyr-installation---upgrade-guides/zephyr-on-premise-production-installation/set-up-zephyr-data-center-cluster/5--configure-load-balancer.html
In order for your cluster to work efficiently, you need to use a load balancer. A load balancer is a software- or hardware-based solution you use to distribute incoming traffic across your servers. You can use any load balancer available on the market and configure it as your needs dictate. The only requirement is that you use the sticky session feature, which ensures that all the requests from a user are sent to the same instance during the session. The timeout of sticky sessions must be 90 minutes.
The scheme below illustrates a cluster architecture in which a load balancer is used:
Â
If you use an Elasticsearch cluster in Zephyr Data Center, there is no need to use an external load balancer, as Elasticsearch used in a cluster has the load balancing capability.
Below is a sample load balancer configuration:
Health check path: /flex/version
Port: 80
Success code: 200
Interval: 60
Sticky sessions: Enabled
Stickiness duration: 90 min
Deregistration delay: 300
Load balancing algorithm: Round-robin
Starting Release 8.2, Zephyr Enterprise documentation is moving from its current location on Atlassian to a dedicated, standalone Zephyr Enterprise Documentation page. https://support.smartbear.com/zephyr-enterprise/docs/en/welcome-to-zephyr-enterprise.html