In additions to all the bugs and improvements done to the code and plugins, the following new features are available when you upgrade from v3.2 to v4.0. For details on what has changed to existing features and configurations that might affect your upgrade, please see the Upgrading to v4.0.x document.
| Table of Contents |
|---|
Tagging disks in storage.config
...
The following configurations have been added to control this feature (the default values are shown):
| Code Block |
|---|
CONFIG proxy.config.http.flow_control.enabled INT 0
CONFIG proxy.config.http.flow_control.high_water INT 65536
CONFIG proxy.config.http.flow_control.low_water INT 65536
|
...
It is now possible to set thread affinity for the main worker threads. This can improve performance, particular on NUMA systems. This is configured via
| Code Block |
|---|
CONFIG proxy.config.exec_thread.affinity INT 1
|
In addition, you can also control how large the memory pools for each thread is, via a new configuration (default is 512):
| Code Block |
|---|
CONFIG proxy.config.allocator.thread_freelist_size INT 512
|
...
When Traffic Server starts, we load meta-data information from the cache. For very large caches, this can take a fairly long time (several seconds). During this load and initialization time, the server will by default proxy requests to the origin. A new configuration has been added, which prevents proxying while the cache is being initialized:
| Code Block |
|---|
CONFIG proxy.config.http.wait_for_cache INT 1
|
...
A new configuration option is added, which lets you control the size of the chunk sizes for content that is Transfer-Encoding with chunking (default value shown):
| Code Block |
|---|
CONFIG proxy.config.http.chunking.size INT 4096
|
...
In previous versions of Apache Traffic Server, content with empty bodies were never cacheable, regardless of what the HTTP header said. We now provide a new option, which allows this type of content to (possibly) be cached. This is particularly useful for caching e.g. redirect responses which has no body. The new configuration is (default is off):
| Code Block |
|---|
CONFIG proxy.config.http.cache.allow_empty_doc INT 0
|
...
A new feature and configuration allows for objects to be stored in more than one cluster member. The new configuration is (default off):
| Code Block |
|---|
CONFIG proxy.config.http.cache.cluster_cache_local INT 0
|
...
Resolving the IP address of an origin server can be set to prefer IP address families in specific orders, both globally and on a per port basis.
| Code Block |
|---|
CONFIG proxy.config.hostdb.ip_resolve STRING ipv4;ipv6
|
...
The following configurations are now overridable through plugin APIs and/or the conf_remap.so plugin:
| Code Block |
|---|
proxy.config.http.chunking.size
proxy.config.http.flow_control.enabled
proxy.config.http.flow_control.low_water
proxy.config.http.flow_control.high_water
proxy.config.http.cache.range.lookup
proxy.config.http.normalize_ae_gzip
proxy.config.http.default_buffer_size
proxy.config.http.default_buffer_water_mark
proxy.config.http.request_header_max_size
proxy.config.http.response_header_max_size
proxy.config.http.negative_revalidating_enabled
proxy.config.http.negative_revalidating_lifetime
proxy.config.http.accept_encoding_filter_enable
|
...
The following API has been added for plugins to examine transaction milestone timers:
| Code Block |
|---|
TSReturnCode TSHttpTxnMilestoneGet(TSHttpTxn txnp, TSMilestonesType milestone, TSHRTime *time);
|
...