This article explains what a Traffic Controller weight is in UltraDNS and how it affects traffic distribution within a Traffic Controller pool.
It applies when configuring load balancing behavior across multiple resources.
When to Use This Article
- You are configuring a Traffic Controller pool.
- You need to distribute traffic unevenly between resources.
- You want to understand how weighted load balancing works.
What a Traffic Controller Weight Represents
A Traffic Controller weight determines the proportion of traffic directed to a specific resource within a pool.
Each resource in the pool is assigned a numeric weight, and traffic is distributed based on the relative weight values of all active resources.
The weight does not represent a percentage directly. Instead, traffic is allocated proportionally.
For example, if one resource has a weight of 10 and another has a weight of 20, the second resource will receive approximately twice as much traffic as the first, assuming both are healthy.
How Weighted Distribution Works
- If all pool records have equal weights, traffic is distributed evenly.
- If weights differ, traffic is distributed proportionally based on the ratio of weights.
- If a resource becomes unavailable, traffic is redistributed among the remaining healthy resources.
How to Configure a Traffic Controller Weight
- Log in to the UltraDNS portal.
- Navigate to the domain using Traffic Controller.
- Select the Traffic Controller pool.
- Edit the desired pool record.
- Enter the desired weight value for that record.
- Save the changes.
Verification
After updating weights, monitor traffic behavior using reporting tools or application metrics.
Traffic distribution should reflect the proportional ratio of the configured weights among healthy pool members.
Important Notes
- Weights apply only to healthy resources.
- Changing weights does not immediately shift all traffic due to DNS caching and TTL behavior.
- Weights are relative values, not fixed percentages.