What link costs are
Link costs let you prioritize which data center site provides a requested service when two or more data center sites exist. You can adjust link costs to reflect latency between sites.
-
Link costs are used to prioritize which object copy is used to fulfill object retrievals.
-
Link costs are used by the Grid Management API and the Tenant Management API to determine which internal StorageGRID services to use.
-
Link costs are used by the deprecated Connection Load Balancer (CLB) service on Gateway Nodes to direct client connections. See How load balancing works - CLB service.
The diagram shows a three site grid that has link costs configured between sites:
-
The CLB service on Gateway Nodes equally distribute client connections to all Storage Nodes at the same data center site and to any data center sites with a link cost of 0.
In the example, a Gateway Node at data center site 1 (DC1) equally distributes client connections to Storage Nodes at DC1 and to Storage Nodes at DC2. A Gateway Node at DC3 sends client connections only to Storage Nodes at DC3.
-
When retrieving an object that exists as multiple replicated copies, StorageGRID retrieves the copy at the data center that has the lowest link cost.
In the example, if a client application at DC2 retrieves an object that is stored both at DC1 and DC3, the object is retrieved from DC1, because the link cost from DC1 to D2 is 0, which is lower than the link cost from DC3 to DC2 (25).
Link costs are arbitrary relative numbers with no specific unit of measure. For example, a link cost of 50 is used less preferentially than a link cost of 25. The table shows commonly used link costs.
Link | Link cost | Notes |
---|---|---|
Between physical data center sites |
25 (default) |
Data centers connected by a WAN link. |
Between logical data center sites at the same physical location |
0 |
Logical data centers in the same physical building or campus connected by a LAN. |