™

Administrator's Guide

Configuring the Cache

The Traffic Server cache consists of a high-speed object database called the object store that indexes objects according to URLs and their associated headers.

This chapter discusses the following topics:

  • The Traffic Server Cache
  • The RAM Cache
  • Changing the Size of the RAM Cache
  • Changing Cache Capacity
  • Partitioning the Cache
  • Configuring the Cache Object Size Limit
  • Clearing the Cache
  • Removing an Object From the Cache
  • Inspecting the Cache

The Traffic Server Cache

The Traffic Server cache consists of a high-speed object database called the object store. The object store indexes objects according to URLs and associated headers. This enables Traffic Server to store, retrieve, and serve not only web pages, but also parts of web pages - which provides optimum bandwidth savings. Using sophisticated object management, the object store can cache alternate versions of the same object (versions may differ because of dissimilar language or encoding types). It can also efficiently store very small and very large documents, thereby minimizing wasted space. When the cache is full, Traffic Server removes stale data to ensure the most requested objects are kept readily available and fresh.

Traffic Server is designed to tolerate total disk failures on any of the cache disks. If the disk fails completely, then Traffic Server marks the entire disk as corrupt and continues using the remaining disks. An alarm is then created to indicate which disk failed. If all of the cache disks fail, then Traffic Server goes into proxy-only mode.

You can perform the following cache configuration tasks:

  • Change the total amount of disk space allocated to the cache: refer to Changing Cache Capacity.
  • Partition the cache by reserving cache disk space for specific protocols and origin servers/domains: refer to Partitioning the Cache.
  • Delete all data in the cache: refer to Clearing the Cache.

The RAM Cache

Traffic Server maintains a small RAM cache of extremely popular objects. This RAM cache serves the most popular objects as quickly as possible and reduces load on disks, especially during temporary traffic peaks. You can configure the RAM cache size to suit your needs, as described in Changing the Size of the RAM Cache below.

Changing the Size of the RAM Cache

Traffic Server provides a dedicated RAM cache for fast retrieval of popular small objects. The default RAM cache size is automatically calculated based on the number and size of the cache partitions you have configured. If you've partitioned your cache according to protocol and/or hosts, then the size of the RAM cache for each partition is proportional to the size of that partition.

You can increase the RAM cache size for better cache hit performance. However, if you increase the size of the RAM cache and observe a decrease in performance (such as increased latencies), then it's possible that the operating system requires more memory for network resources. In such instances, you should return the RAM cache size to its previous value.

To change the RAM cache size:
  1. Stop Traffic Server.
  2. In a text editor, open the records.config file located in the Traffic Server config directory.
  3. Edit the following variable:
    4. Variable Description
    proxy.config.cache.ram_cache.size Set this variable to specify the size of the RAM cache.
    The default value of -1 means that the RAM cache is automatically sized at approximately 1MB per gigabyte of disk.
  4. Save and close the records.config file.
  5. Restart Traffic Server. If you increase the RAM cache to a size or 1GB or more, then restart with the start_traffic_server command (refer to Starting Traffic Server).

 

Changing Cache Capacity

You can increase or reduce the total amount of disk space allocated to the cache without clearing the content. To check the size of the cache (in bytes), enter the command traffic_line -r proxy.process.cache.bytes_total.

Increasing Cache Capacity

To increase the total amount of disk space allocated to the cache on existing disks or to add new disks to a Traffic Server node, follow the steps below:

  1. Stop Traffic Server.
  2. Add hardware, if necessary.
  3. Edit the Traffic Server storage.config file: increase the amount of disk space allocated to the cache on existing disks or describe the new hardware you are adding (refer to storage.config).
  4. If you add a new disk, then you must edit the /etc/rc.d/init.d/traffic_server file to add a raw disk binding. Instructions for adding a raw disk binding are located in the Traffic Server storage.config file.
  5. Restart Traffic Server.

Reducing Cache Capacity

To reduce the total amount of disk space allocated to the cache on an existing disk or to remove disks from a Traffic Server node, follow the steps below:

  1. Stop Traffic Server.
  2. Remove hardware, if necessary.
  3. Edit the Traffic Server storage.config file: reduce the amount of disk space allocated to the cache on existing disks or delete the reference to the hardware you're removing (refer to storage.config).
  4. If you remove a disk, then you must edit the /etc/rc.d/init.d/traffic_server file to remove the raw disk binding for the disk.
  5. Restart Traffic Server.

IMPORTANT: In the storage.config file, a formatted or raw disk must be at least 128 MB.

Partitioning the Cache

You can manage your cache space more efficiently and restrict disk usage by creating cache partitions with different sizes for specific protocols. You can further configure these partitions to store data from specific origin servers and/or domains. The partition configuration must be the same on all nodes in a cluster.

Creating Cache Partitions for Specific Protocols

You can create separate partitions for your cache that vary in size to store content according to protocol. This ensures that a certain amount of disk space is always available for a particular protocol. Traffic Server currently supports the http partition type for HTTP objects.

To partition the cache according to protocol:
  1. In a text editor, open the partition.config file located in the Traffic Server config directory.
  2. Enter a line in the file for each partition you want to create (refer to partition.config).
  3. Save and close the partition.config file.
  4. Restart Traffic Server.

Making Changes to Partition Sizes and Protocols

After you've configured your cache partitions based on protocol, you can make changes to the configuration at any time. Before making changes, note the following:

  • You must stop Traffic Server before you change the cache partition size and protocol assignment.
  • When you increase the size of a partition, the contents of the partition are not deleted However, when you reduce the size of a partition, the contents of the partition are deleted.
  • When you change the partition number, the partition is deleted and then recreated, even if the size and protocol type remain the same.
  • When you add new disks to your Traffic Server node, partition sizes specified in percentages will increase proportionately.
  • A lot of changes to partition sizes might result in disk fragmentation, which affects performance and hit rate. You should clear the cache before making many changes to cache partition sizes (refer to Clearing the Cache).

Partitioning the Cache According to Origin Server or Domain

After you have partitioned the cache according to size and protocol, you can assign the partitions you created to specific origin servers and/or domains. You can assign a partition to a single origin server or to multiple origin servers. However, if a partition is assigned to multiple origin servers, then there is no guarantee on the space available in the partition for each origin server. Content is stored in the partition according to popularity. In addition to assigning partitions to specific origin servers and domains, you must assign a generic partition to store content from all origin servers and domains that are not listed. This generic partition is also used if the partitions for a particular origin server or domain become corrupt. If you do not assign a generic partition, then Traffic Server will run in proxy-only mode.

Note: You do not need to stop Traffic Server before you assign partitions to particular hosts or domains. However, this type of configuration is time-consuming and can cause a spike in memory usage. Therefore, it's best to configure partition assignment during periods of low traffic.

To partition the cache according to hostname and domain:
  1. Configure the cache partitions according to size and protocol, as described in Creating Cache Partitions for Specific Protocols.
  2. Create a separate partition based on protocol for each host and domain, as well as an additional generic partition to use for content that does not belong to these origin servers or domains. The partitions do not need to be the same size.
  3. In a text editor, open the hosting.config file located in the Traffic Server config directory.
  4. Enter a line in the file to allocate the partition(s) used for each origin server and/or domain (refer to hosting.config).
  5. Assign a generic partition to use for content that does not belong to any of the origin servers or domains listed in the file. If all partitions for a particular origin server become corrupt, then Traffic Server will also use the generic partition to store content for that origin server (see hosting.config).
  6. Save and close the hosting.config file.
  7. Navigate to the Traffic Server bin directory.
  8. Run the command traffic_line -x to apply the configuration changes.

Configuring the Cache Object Size Limit

By default, Traffic Server allows objects of any size to be cached. You can change the default behavior and specify a size limit for objects in the cache via the steps below:

  1. In a text editor, open the records.config file located in the Traffic Server config directory.
  2. Edit the following variable:
    Variable Description
    proxy.config.cache.max_doc_size Set this variable to specify the maximum size allowed for objects in the cache in bytes.
    Enter 0 (zero) if you do not want a size limit.
  3. Save and close the records.config file.
  4. Navigate to the Traffic Server bin directory.
  5. Run the command traffic_line -x to apply the configuration changes.

Clearing the Cache

When you clear the cache, you remove all data from the entire cache - including data in the host database. You should clear the cache before performing certain cache configuration tasks, such as partitioning. You cannot clear the cache when Traffic Server is running.

To clear the cache:
  1. Stop Traffic Server (refer to Stopping Traffic Server).
  2. Enter the following command to clear the cache:
    traffic_server -Cclear
    The clear command deletes all data in the object store and the host database. Traffic Server does not prompt you to confirm the deletion.
  3. Restart Traffic Server (refer to Starting Traffic Server).

Removing an Object From the Cache

Traffic Server accepts the custom HTTP request method PURGE when removing a specific object from cache. If the object is found in the cache and is successfully removed, then Traffic Server responds with a 200 OK HTTP message; otherwise, a 404 File Not Found message is returned.

In the following example, Traffic Server is running on the domain example.com and you want to remove the image remove_me.jpg from cache:

$ curl -X PURGE -v "http://example.com/remove_me.jpg"

* About to connect() to example.com port 80 (#0)
* Trying 192.0.32.11... connected
* Connected to example.com (192.0.32.11) port 80 (#0)

> PURGE /remove_me.jpg HTTP/1.1
> User-Agent: curl/7.19.7
> Host: example.com
> Accept: */*
>
< HTTP/1.1 200 Ok
< Date: Thu, 08 Jan 2010 20:32:07 GMT
< Connection: keep-alive

The next time Traffic Server receives a request for the removed object, it will contact the origin server to retrieve it (i.e., it has been purged from the Traffic Server cache).

Note: The procedure above only removes an object from a specific Traffic Server cache. Users may still see the old (removed) content if it was cached by intermediary caches or by the end-users' web browser.

Inspecting the Cache

Traffic Server provides a Cache Inspector utility that enables you to view, delete, and invalidate URLs in the cache (HTTP only). The Cache Inspector utility is a powerful tool that's capable of deleting all the objects in your cache; therefore, make sure that only authorized administrators are allowed to access this utility. To control which hosts have access via the mgmt_allow.config file, see Controlling Host Access to Traffic Manager.

Accessing the Cache Inspector Utility

To access the Cache Inspector utility, follow the steps below:

  1. In a text editor, open the records.config file located in the Traffic Server config directory.
  2. Add the following variable at the end of the file:
    CONFIG proxy.config.http_ui_enabled INT 1
  3. To access the cache inspector in reverse proxy mode, you must add a remap rule to remap.config to expose the URL.
    For example:
    map http://yourhost.com/myCI http://{cache} @action=allow @src_ip=corp_internal_address
  4. From the Traffic Server bin directory, enter the following command to re-read the configuration file:
    traffic_line -x
  5. Open your web browser and configure it to use your Traffic Server as a proxy server. Type the following URL:
    http://{cache}
  6. The Cache page opens (see Using the Cache Page below).

Using the Cache Page

The Cache page provides several options that enable you to view and delete the contents of your cache:

  • Click Lookup url to search for a particular URL in the cache. When Traffic Server finds the URL in the cache, it displays details about the object that corresponds to the URL (such as the header length and the number of alternates). From the display page, you can delete the URL from the cache.
  • Click Delete url to delete a particular URL or list of URLs from the cache. Traffic Server indicates if a delete is successful.
  • Click Regex lookup to search for URLs that match one or more regular expressions. From the display page, you can delete the URLs listed.
    For example, enter the following to search for all URLs that end in html and are prefixed with http://www.dianes.com:
    http://www.dianes.com/.*\.html$
  • Click Regex delete to delete all URLs that match a specified regular expression.
    For example, enter the following to delete all HTTP URLs that end in html:
    http://.*\.html$
  • Click Regex invalidate to invalidate URLs that match a specified regular expression. When you invalidate a URL, Traffic Server marks the object that corresponds to the URL as stale in the cache. Traffic Server then contacts the origin server to check if the object is still fresh (revalidates) before serving it from the cache.

Note: Only one administrator should delete and invalidate cache entries from the Cache page at any point in time. Changes made by multiple administrators at the same time can lead to unpredictable results.

  • Overview
  • Getting Started
  • HTTP Proxy Caching
  • Explicit Proxy Caching
  • Reverse Proxy and HTTP Redirects
  • Hierarchical Caching
  • Configuring the Cache
  • Monitoring Traffic
  • Configuring Traffic Server
  • Security Options
  • Working with Log Files
  • Traffic Line Commands
  • Event Logging Formats
  • Configuration Files
  • Traffic Server Error Messages
  • FAQ and Troubleshooting Tips
  • Traffic Server 管理员指南 (PDF)
Copyright © 2013 The Apache Software Foundation. Licensed under the Apache License, Version 2.0. Apache Traffic Server, Apache, the Apache Traffic Server logo, and the Apache feather logo are trademarks of The Apache Software Foundation.