hosting.config

The hosting.config file lets you assign cache partitions to specific origin servers and domains so that you can manage your cache space more efficiently and restrict disk usage.

For step-by-step instructions on partitioning the cache according to origin servers and domains, see Partitioning the cache according to origin server or domain.


	Note Before you can assign cache partitions to specific origin servers and domains, you must partition your cache according to size and protocol in the partition.config file. For more about cache partitioning, see Partitioning the cache. For a description of the partition.config file, see partition.config.

After you modify the hosting.config file, run content_line -x from the Content Gateway bin directory to apply the changes. When you apply the changes to a node in a cluster, Content Gateway automatically applies the changes to all nodes in the cluster.


	Important The partition configuration must be the same on all nodes in a cluster.

Format

Each line in the hosting.config file must have one of the following formats:

hostname=hostname partition=partition_numbers

domain=domain_name partition=partition_numbers

where:

hostname is the fully qualified hostname of the origin server whose content you want to store on a particular partition (for example, www.myhost.com).

domain_name is the domain whose content you want to store on a particular partition (for example, mydomain.com).

partition_numbers is a comma-separated list of the partitions on which you want to store the content that belongs to the origin server or domain listed. The partition numbers must be valid numbers listed in the partition.config file (see partition.config).


	Note If you want to allocate more than one partition to an origin server or domain, enter the partitions in a comma-separated list on one line. The hosting.config file cannot contain multiple entries for the same origin server or domain.

Generic Partition

When configuring the hosting.config file, you must assign a generic partition to use for content that does not belong to any of the origin servers or domains listed. If all partitions for a particular origin server become corrupt, Content Gateway uses the generic partition to store content for that origin server.

The generic partition must have the following format:

hostname=* partition=partition_numbers

where partition_numbers is a comma-separated list of generic partitions.

Examples

The following example configures the proxy to store content from the domain mydomain.com in partition 1 and content from www.myhost.com in partition 2. The proxy stores content from all origin servers in partitions 3 and 4.

domain=mydomain.com partition=1

hostname=www.myhost.com partition=2

hostname=* partition=3,4