Google Global Cache Beta

Multinode Deployment Guide

Revised: June 9, 2011

Option 1a: Multiple nodes in a single location

If the nodes are in the same metro or a proximate geographical location, they will be deployed in
a load-balanced configuration as part of single network location. This will provide increased
reliability and capacity.
Nodes in different metros may also be configured this way, provided the nodes are within 10 ms
RTT of each other, and if you dont mind which of the nodes your users get served from.
What prefixes should I announce?
In this configuration, you must announce the same user & resolver prefixes to each node.
Failover and Overflow
Failover in this case will be to the remaining healthy node(s) in the same network location. If the
load exceeds the capacity of the remaining node(s), it will overflow to your chosen failover
location - either a GGC node in another network location (if you have GGC nodes in more than
one location) or to caches on Googles network (see note: Failover Locations).

Option 1b: Multiple nodes in a single location + sharding

The model described in (1a) can be enhanced to further reduce your peering/transit traffic. By
splitting or sharding the cached content across pairs of cache nodes, the content will only be
downloaded once for each pair of nodes, rather than for each individual GGC node. This can
also be extended to a second pair of nodes, with the catalogue split 4 ways.
If a node fails in a sharded configuration, failover will be to the specified failover location.
The GGC support team will contact you to discuss this option, based on the performance of
your nodes.

Google Confidential

Option 2: Nodes in multiple locations, with regionalized user & resolver prefixes
If the nodes are not in the same geographical location and will serve distinct sets of users, they
will be configured as separate network locations.
What prefixes should I announce?
In this configuration, you must announce unique user & resolver prefixes to each node.
What if only have one resolver prefix for all of my users?
See Option 3, below.
Failover and Overflow
Failover and overflow will be to your preferred failover location - either a GGC node in another
network location or to caches on Googles network (see note: Failover Locations).

Option 3: Nodes in multiple locations, but with same resolvers

As per Option 2, the nodes will be configured as separate network locations.
What prefixes should I announce?
In this configuration, you should split or regionalize the user prefix announcements to each node.
Your resolver prefix must be announced to the node serving the largest user population only.
Please note that even if you announce the same resolver prefix to more than one node it will only
get mapped to one GGC node.
Failover and Overflow
Failover and overflow will be to your preferred failover location - either a GGC node in another
network location or to caches on Googles Network (see note Failover Locations).

Failover Locations
If you have GGC nodes in two or more network locations, you can specify a primary and
secondary failover location for each node, meaning that in the event of a node failing or
overflowing, GGC will first try and serve the traffic from these locations - provided they are
available and have capacity - before redirecting the requests to caches on Googles network.
If you would like to have nodes failover and back each other up in this manner, please
communicate your preferences to the GGC support team (ggc@google.com).
Google Confidential

An example failover matrix:

Primary Failover

Secondary Failover

mynode-aaa1

mynode-bbb1

Google

mynode-bbb1

mynode-aaa1

Google

mynode-ccc1

Google

n/a

Confidential: For Customer Use Only

2011 Google Inc. All Rights Reserved.

Google Confidential