
Using Envoy
Dynamic site weights can vary from 50% to 150% of the assigned initial weights. To optimize GeoCluster
performance, you might need to adjust the initial weights of the sites in the cluster based on their
performance.
Site weights can range from 10 to 200. When you set up sites in a GeoCluster, you should set each site’s
initial weight value in proportion to its capacity for handling requests. It is not necessary for all of the initial
weights in a cluster to add up to any particular number.
6. Click on Commit to add the GeoSite instance. The instance will appear beneath the GeoCluster on the left
navigational pane as shown below.
7. Select additional options for the GeoSite instance by clicking the GeoSite instance from the left
navigational pane to display the Configuration Required screen (tab).From this screen all configuration
options can be modified.
l Default - Designates this site as the default site for the GeoCluster. Envoy load balances to
the default site whenever it cannot choose a site based on the GQP probe information it gets
from the sites. This can happen, for example, when GQP probe responses are not received
from any site, when the resource (cluster) is down at all available sites, etc. If no default site
is selected for a GeoCluster and all sites are down, then Envoy sends a null response to the
client DNS.
l Hot Spare - When enabled, no traffic will be routed to the site unless there are no other sites
available. Default value is disabled.
l Disabled - When turned on, no traffic will be routed to the site. Default value is off.
Deleting a GeoSite Instance (GUI)
530
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
Comentarios a estos manuales