Weighted Random Load Balancing with Data Center Stickiness property
Use this property to distribute traffic using percentages you configure. The data center assignments are sticky, meaning that a given name server stays mapped to the same data center unless that data center goes down.
- On the Traffic Management Domains page, select the domain for which you want to add a property and click Add New Property.
- Enter a name in the Property Name field. This is required.
Select Weighted Random Load
Balancing with Data Center Stickiness from the Property Type
list and enter the following information or accept the defaults:
- Comments (optional)
- DNS TTL
- IP Type
- Minimum Live Percentage (optional)
- Click Add To Change & Next. The Traffic Targets page appears.
- Select the Data Center associated with a traffic target from the menu.
Enter server names or Handout
CNAMEs for each target.
If a handout CNAME is given, traffic distributed to a traffic target will be sent to where the CNAME points. If servers are also given, liveness tests from these servers will be used to determine if the traffic target is available. If no server is given, this traffic target is always considered available. If you have more than one server name, separate them with commas, spaces, or line breaks.
- Enter an IP address or CNAME in the Backup Answer field.
Click Balance All
Targets Evenly to split the load among the targets.
You can manually enter load proportions in the Data Center Weight field of a target, which will be routed to the data center. In this example the split is 40 percent for Target 2 and 60 percent for Target 1.
To add a new target at this
stage, click Add New
Target. If you do not have an available data center, a clone for
an existing one is created.
To enable or disable a target, use the slider. To remove a target, click X.
- When you complete the target information, click Add To Change List & Next. The Liveness Test page appears.
Enter the following information
for at least one test, or click Skip to proceed
to the Review page. You can create a test later. This example uses the HTTP
protocol. Other protocols will have different or fewer fields to fill out. See
Liveness Test for more information on these fields.
- Test Name (required)
- Test Interval
- Test Timeout
- Port: specify the port number for requesting the test object
- Protocol: select a type from the menu (for example, HTTP, FTP, TCP)
- Test Object Path (optional): only enter the local part of the URL for the test object (for example, /data/results/test.html)
- Host Header (optional)
- HTTP/FTP errors: Select the responses you want to consider for server failures.
- Authentication: If you are using password authentication, provide a username and password.
Click Add To Change List &
Next. The Review page appears.
On the Review page you can view the basic property settings, traffic targets, and liveness
tests and edit the settings if you want to make revisions.Note: Akamai will use the servers specified in the data center to determine if the traffic target is available. If the liveness test fails on all the servers in a data center, Akamai will stop sending traffic. Also, if a handout CNAME is given, traffic distributed to a traffic target will be sent to where the CNAME points. If servers are also given liveness tests from these servers will be used to determine if the traffic target is available. If no server is given, this traffic target is always considered available.
- Click Add To Change List. The Properties tab appears. A green check mark will appear next to the new property.
- Click Review Change List.
Review the Change List Dialog
changes, validate them, add a required comment, and click Activate Domain
to save them.
See Change List Detail Dialog for more information.