Create an Azure Load Balancer
In a production environment, two redundant Hyper-Q VMs in conjunction with a load balancer provide high-availability and fault-tolerance. For Hyper-Q, you must use a public load balancer. To learn about the different load balancers, and how to create and configure one for use with Hyper-Q, see the following article in the Microsoft Azure documentation:
Quickstart: Create a public load balancer to load balance VMs using the Azure portal
The following procedure summarizes how to configure an Azure load balancer for use with Hyper-Q. Refer to the Azure documentation for information specific to the load balancer you are using for your deployment.
Sign in to the Azure portal at: https://portal.azure.com
In the search box at the top of the Azure portal, type Load balancer, and then select Load balancers in the search results.
In the Load balancer page, select Create.
In the Basics tab of the Create load balancer page, enter, or select the following information.
Table 2.Setting
Value
Subscription
Select the same subscription in which you deployed the Hyper-Q VMs.
Resource group
Select the same resource group in which you deployed the Hyper-Q VMs.
Name
Type a name with which to identify the load balancer.
Region
Select a region appropriate to the location of the Azure Synapse database and Hyper-Q deployment.
Type
Select Public.
SKU
Leave the default value of Standard.
Tier
Leave the default value of Regional.
Click Review + Create.
When the deployment completes the page displays the message Your deployment is complete.
Click Go to resources.
From the Resources page you will configure:
Backend pools.
Health probes.
Load balancing rules.
Configure Backend Pools
The backend pool defines the group of resources that serve traffic for a given load-balancing rule.
In the Backend pools tab, select + Add.
The Add backend pool page displays.
Enter a name for the backend pool in the Name field.
Select the virtual network for the Hyper-Q VMs from the Virtual network drop-down list and click Add.
The Virtual network drop-down lists all the virtual machines deployed in the Vnet which have standard IP addresses. You must select the two virtual machines on which Hyper-Q is installed and click Add.
Select both of the Hyper-Q VMs, and select Add.
Select the blue Review + create button at the bottom of the page.
Select Create.
When the deployment completes, the two Hyper-Q VMs will be attached to the backend pools.
Configure Health Probes
A health probe is used to determine the health status of the Hyper-Q VM instances in the backend pool. During load balancer creation, you configure a health probe for the load balancer to use. The health probe determines if a Hyper-Q VM instance is healthy and can receive traffic.
Select Health probes and then select Add to add a new health probe.
On the Add health probe page, fill out the required information for the probe.
From the Protocol drop-down select TCP.
Enter 1025 in the Port text field.
Select OK to confirm the configuration choices.
Configure Load Balancing Rules
A load balancer rule defines how incoming traffic is distributed to the Hyper-Q VM instances within the backend pool. A load-balancing rule maps a given frontend IP configuration and port to multiple backend IP addresses and ports.
Select Load balancing rules and then select Add to add new rules.
On the Add load balancing rule page, fill out the required information for the rules.
Enter or select the following information in the Add load balancing rule page.
Setting
Value
Protocol
TCP
Port
1025
Backend port
1025
Session persistence
Client IP and protocol
Idle timeout (minutes)
30
Click Add to create the load balancer.
Review the load balancing rule configuration and ensure it is correct.
Validate the Load Balancer Configuration
Validate the load balancer configuration.
Select Overview.
Find the public IP address for the load balancer on the Overview screen.
Copy the public IP address, and then paste it into the SQL client of your choosing to create a connection through the load balancer to Hyper-Q and the underlying data warehouse.
Refer to the documentation for your specific SQL client to learn how to configure a connection.
Verify that the SQL client connects to the data warehouse.